Triple
T5007573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troy |
E112533
|
entity |
| Predicate | hasArchaeologicalLayer |
P31670
|
FINISHED |
| Object | Troy I |
E112533
|
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: Troy I | Statement: [Troy, hasArchaeologicalLayer, Troy I]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Troy I Context triple: [Troy, hasArchaeologicalLayer, Troy I]
-
A.
Troy
Troy is a historic city in eastern New York State, known for its 19th-century architecture and role in the Industrial Revolution as a major manufacturing center.
-
B.
Troy
chosen
Troy is the legendary ancient city in Asia Minor that was the focal point of the Trojan War in Greek and Roman mythology.
-
C.
Troy
Troy is a masculine given name of ancient origin, famously borne by former NFL quarterback Troy Aikman.
-
D.
Troy
Troy is a 2004 epic historical war film loosely based on Homer's Iliad, depicting the legendary conflict between the Greeks and Trojans.
-
E.
Troy
Troy is a suburban city in Michigan known for its strong business community, shopping centers, and role as a key part of the Detroit metropolitan area.
- 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd72e8a0308190a47d81943ad85bba |
completed | March 20, 2026, 4:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be9266314881909dfb710c5b5c8f65 |
completed | March 21, 2026, 12:43 p.m. |
Created at: March 20, 2026, 1:35 p.m.