Triple

T23450588
Position Surface form Disambiguated ID Type / Status
Subject Battle of Dara E567768 entity
Predicate hasLocation P40 FINISHED
Object Dara 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: Dara | Statement: [Battle of Dara, hasLocation, Dara]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dara
Context triple: [Battle of Dara, hasLocation, Dara]
  • A. Dara chosen
    Dara was a strategically important fortified city in northern Mesopotamia that served as a key Byzantine stronghold against the Sasanian Empire.
  • B. Dara
    Dara is a given name most prominently associated with Dara Khosrowshahi, the Iranian-American businessman and CEO of Uber.
  • C. Darda
    Darda is a village and municipality in the Baranja region of eastern Croatia, known for its multicultural population and historical heritage.
  • D. Anar Dara
    Anar Dara is a town and district center in western Afghanistan known for its agricultural surroundings and location within Farah Province.
  • E. Djao
    Djao is an alternative name for the Yao, an ethnic group found primarily in parts of China and Southeast Africa, known for their distinct cultural traditions and languages.
  • 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_69e2458b4c888190b1d7998f9862a558 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f1a64d3e9c8190a2596b067c4f5061 completed April 29, 2026, 6:33 a.m.
Created at: April 17, 2026, 5:52 p.m.