Triple

T34492509
Position Surface form Disambiguated ID Type / Status
Subject Saltmen of Zanjan archaeological site E885505 entity
Predicate hasPreservationAgent P204028 FINISHED
Object salt LITERAL FINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: salt | Statement: [Saltmen of Zanjan archaeological site, hasPreservationAgent, salt]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPreservationAgent
Context triple: [Saltmen of Zanjan archaeological site, hasPreservationAgent, salt]
  • A. hasPreservationControls
    Indicates that an entity is subject to specific measures or mechanisms intended to preserve, protect, or maintain it over time.
  • B. hasPreservationNeed
    Indicates that an entity requires specific actions or conditions to be maintained in order to prevent its deterioration or loss.
  • C. hasPreserved
    Indicates that one entity has kept another entity intact, unchanged, or maintained in its original or functional state over time.
  • D. hasPreservationActivity
    Indicates that an entity is involved in, or associated with, a specific preservation-related action or process.
  • E. hasSubjectOfPreservation
    Indicates that something is the specific focus or object being preserved or conserved within a preservation relationship.
  • F. None of above. chosen

Provenance (4 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69f349cafcec8190997b45b3fdc16c27 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_6a030e31e01881909c6032532cd3c31a completed May 12, 2026, 11:25 a.m.
PD Predicate disambiguation batch_6a030dadea008190abe0a5652784bdd6 completed May 12, 2026, 11:23 a.m.
PDg Predicate description generation batch_6a030e30ec5881908b59d8e85b7feaa5 completed May 12, 2026, 11:25 a.m.
Created at: May 1, 2026, 2:01 a.m.