Triple
T16840624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diomedes |
E409398
|
entity |
| Predicate | enemyOf |
P437
|
FINISHED |
| Object | Aeneas |
E110997
|
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: Aeneas | Statement: [Diomedes, enemyOf, Aeneas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aeneas Context triple: [Diomedes, enemyOf, Aeneas]
-
A.
Aeneas
chosen
Aeneas is a Trojan hero in Greco-Roman mythology, renowned as the legendary ancestor of the Romans and the pious protagonist of Virgil’s epic poem the Aeneid.
-
B.
Ascanius
Ascanius is the legendary son of Aeneas in Roman mythology, regarded as an ancestor of the founders of Rome and a symbol of its destined imperial future.
-
C.
Turnus
Turnus is the hot-headed Rutulian prince and chief antagonist of Aeneas in Virgil’s epic poem the Aeneid.
-
D.
Anchises
Anchises is a figure in Greek and Roman mythology best known as the mortal father of the Trojan hero Aeneas and a lover of the goddess Aphrodite.
-
E.
Brutus of Troy
Brutus of Troy is a legendary Trojan exile in medieval British mythology, traditionally credited as the founder and first king of Britain.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b3508ecc81909c0af299e07f4b31 |
completed | April 18, 2026, 4:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00bb177e288190b525e6d239892d26 |
completed | May 10, 2026, 5:06 p.m. |
Created at: April 10, 2026, 5:24 a.m.