Triple
T8479903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lavinium |
E200487
|
entity |
| Predicate | mentionedBy |
P831
|
FINISHED |
| Object | Vergil |
E37288
|
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: Vergil | Statement: [Lavinium, mentionedBy, Vergil]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vergil Context triple: [Lavinium, mentionedBy, Vergil]
-
A.
Iulus
Iulus is a figure in Roman mythology, traditionally regarded as the son of Aeneas and the legendary ancestor of the Julian family, including Julius Caesar.
-
B.
Virgil
chosen
Virgil was a renowned Roman poet of the Augustan period, best known for composing the epic Aeneid, which became a cornerstone of Latin literature.
-
C.
Virgil
Virgil is the given first name of American astronaut Gus Grissom, one of NASA’s original Mercury Seven.
-
D.
Thascius
Thascius is the family name of the early Christian bishop and martyr Cyprian of Carthage.
-
E.
Semo Sancus
Semo Sancus is an ancient Italic god, particularly revered by the Sabines and early Romans as a divine guarantor of oaths, treaties, and good faith.
- 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_69ca831b17988190a1f3f3413d57b820 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe5232d008190ae55b982f5fc9e8b |
completed | March 31, 2026, 3:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce3a22d6e481908bdb0b9cc0df0113 |
completed | April 2, 2026, 9:42 a.m. |
Created at: March 30, 2026, 6:12 p.m.