Triple

T21058943
Position Surface form Disambiguated ID Type / Status
Subject Chorus of citizens of Pherae E518800 entity
Predicate locatedInFiction P40 FINISHED
Object Pherae 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: Pherae | Statement: [Chorus of citizens of Pherae, locatedInFiction, Pherae]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pherae
Context triple: [Chorus of citizens of Pherae, locatedInFiction, Pherae]
  • A. Pherae chosen
    Pherae was an ancient Greek city in Thessaly known for its political influence and as the seat of the powerful tyrant Jason of Pherae.
  • B. Aegium
    Aegium was an important ancient Greek city in the region of Achaea, known as a political and religious center, especially during the Hellenistic period.
  • C. Troesmis
    Troesmis was an ancient Roman military and urban settlement in the province of Moesia, strategically located near the Danube River in what is now Romania.
  • D. Eleutherae
    Eleutherae was an ancient Greek city on the border between Attica and Boeotia, known for its sanctuary of Dionysus and its strategic location near Mount Cithaeron.
  • E. Coronea
    Coronea was an ancient city of Boeotia in central Greece, known for its strategic location and role in several classical Greek battles.
  • 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_69e0b5053ac48190921529544959e906 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e6fd8236b481908eebfaeeb2aa63e6 completed April 21, 2026, 4:30 a.m.
Created at: April 16, 2026, 2:37 p.m.