Triple

T16112632
Position Surface form Disambiguated ID Type / Status
Subject Proto-Elamite period E390916 entity
Predicate hasMajorSite P5003 FINISHED
Object Susa E86185 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: Susa | Statement: [Proto-Elamite period, hasMajorSite, Susa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Susa
Context triple: [Proto-Elamite period, hasMajorSite, Susa]
  • A. Susa chosen
    Susa was an ancient city in southwestern Iran that served as a major political and administrative center for several empires, including the Achaemenid Persians.
  • B. Susa
    Susa is an ancient town in the Piedmont region of northwestern Italy, historically significant as a key Alpine gateway between Italy and France.
  • C. Ecbatana
    Ecbatana is an ancient city, traditionally identified with the capital of the Median Empire in northwestern Iran, known from classical sources and biblical texts.
  • D. Arsanjan
    Arsanjan is a small city in southern Iran known for its agricultural activities and location within the historical and culturally rich Fars region.
  • E. Bishapur
    Bishapur was an ancient Sasanian city in southwestern Iran, renowned for its rock reliefs and archaeological remains that reflect a blend of Persian and Roman architectural influences.
  • 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_69d87f1a8dd881909f1de6ef78849874 completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e20167ee1481909e56dc632bfc0fc5 completed April 17, 2026, 9:46 a.m.
NED1 Entity disambiguation (via context triple) batch_69fffeef277481908ab35bbff06c827a completed May 10, 2026, 3:43 a.m.
Created at: April 10, 2026, 5 a.m.