Triple
T11794997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troad |
E280482
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Ilion |
E731698
|
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: Ilion | Statement: [Troad, contains, Ilion]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ilion Context triple: [Troad, contains, Ilion]
-
A.
Ilion
Ilion is a suburban municipality in the Athens metropolitan area of Greece, located within the West Athens regional unit.
-
B.
West Troy
West Troy is the former name of Watervliet, a small industrial city located along the Hudson River in eastern New York State.
-
C.
Troja
Troja is a district in Prague known for hosting several academic and research facilities, including parts of Charles University’s Faculty of Mathematics and Physics.
-
D.
Troy IX
chosen
Troy IX is the latest and uppermost settlement phase at the archaeological site of Hisarlik, representing the Hellenistic and Roman-era city that succeeded the earlier Bronze Age Troys.
-
E.
Troad
Troad is the historical region in northwestern Asia Minor that encompassed the ancient city of Troy and its surrounding territory.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5a082d08190a42541396a06ed98 |
completed | April 10, 2026, 7:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f0911c2a40819088079fc286e4dc67 |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 8, 2026, 9:42 p.m.