Triple
T11964423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ganymede |
E284755
|
entity |
| Predicate | father |
P120
|
FINISHED |
| Object | Tros |
E950501
|
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: Tros | Statement: [Ganymede, father, Tros]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tros Context triple: [Ganymede, father, Tros]
-
A.
Tros
chosen
Tros is a figure in Greek mythology known as the eponymous founder and king of Troy, from whom the Trojans derive their name.
-
B.
Trogen
Trogen is a municipality in the canton of Appenzell Ausserrhoden in northeastern Switzerland, known for its picturesque setting and traditional Swiss architecture.
-
C.
Dardanos
Dardanos was an ancient town in the Troad region of northwestern Anatolia, known from Greek and Roman sources and associated with early Trojan legends.
-
D.
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.
-
E.
Troy
Troy is a 2004 epic historical war film loosely based on Homer's Iliad, depicting the legendary conflict between the Greeks and Trojans.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903799f948190a5dc4d3822f3ff27 |
completed | April 10, 2026, 2:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f48a83c2448190bb40c199afef2ec2 |
completed | May 1, 2026, 11:12 a.m. |
Created at: April 8, 2026, 9:45 p.m.