Triple

T22051627
Position Surface form Disambiguated ID Type / Status
Subject Tura quarries E544897 entity
Predicate ancientName P2834 FINISHED
Object Tura NE NERFINISHED

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: Tura | Statement: [Tura quarries, ancientName, Tura]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tura
Context triple: [Tura quarries, ancientName, Tura]
  • A. Tura
    Tura is a remote urban-type settlement in central Siberia, Russia, historically serving as an administrative center in the Evenk region.
  • B. Tura
    Tura is a prominent town in the Indian state of Meghalaya, serving as a major administrative, cultural, and economic center in the Garo Hills region.
  • C. Tura chosen
    Tura is a district in southern Cairo, Egypt, historically known for its limestone quarries used in ancient Egyptian monuments.
  • D. Turi
    Turi is a small town and comune in the Apulia region of southern Italy, known for its agricultural production—especially cherries—and its historic architecture.
  • E. Turi
    Turi is a tribe associated with the Karlani Pashtun confederation, traditionally found in regions of Afghanistan and Pakistan.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e32445c8190ab97089b48a130bb completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f1283386f081908b70df81f38a5b1c completed April 28, 2026, 9:35 p.m.
Created at: April 16, 2026, 8:26 p.m.