Triple

T11882415
Position Surface form Disambiguated ID Type / Status
Subject Persian court E282690 entity
Predicate location P40 FINISHED
Object Ecbatana E122204 NE 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: Ecbatana | Statement: [Persian court, location, Ecbatana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ecbatana
Context triple: [Persian court, location, Ecbatana]
  • A. Ecbatana chosen
    Ecbatana is an ancient city, traditionally identified with the capital of the Median Empire in northwestern Iran, known from classical sources and biblical texts.
  • B. Susa
    Susa was an ancient city in southwestern Iran that served as a major political and administrative center for several empires, including the Achaemenid Persians.
  • C. Susa
    Susa is an ancient town in the Piedmont region of northwestern Italy, historically significant as a key Alpine gateway between Italy and France.
  • D. Ctesiphon
    Ctesiphon was an ancient metropolis on the Tigris River that served for centuries as the principal capital of the Parthian and later Sasanian Persian empires.
  • E. Arsanjan
    Arsanjan is a small city in southern Iran known for its agricultural activities and location within the historical and culturally rich Fars region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d6ab2a90b08190a4e818821cc93e6d completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8d39d2934819093b9f7006f45e5cb completed April 10, 2026, 10:40 a.m.
NED1 Entity disambiguation (via context triple) batch_69f417da310c8190aa04df2a316a5dd0 completed May 1, 2026, 3:02 a.m.
Created at: April 8, 2026, 9:44 p.m.