Triple
T14220475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vetranio |
E352476
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Vetranio |
E352476
|
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: Vetranio | Statement: [Vetranio, givenName, Vetranio]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vetranio Context triple: [Vetranio, givenName, Vetranio]
-
A.
Vetranio
chosen
Vetranio was a 4th-century Roman general who briefly ruled as a usurper emperor in the Balkans before abdicating in favor of Constantius II.
-
B.
Vipsanius
Vipsanius is a Roman nomen (family name) associated with members of the Vipsania gens in ancient Rome.
-
C.
Quintillus
Quintillus was a short-reigning 3rd-century Roman emperor who briefly ruled after Claudius Gothicus and before Aurelian during the Crisis of the Third Century.
-
D.
Jovinus
Jovinus was a Roman usurper who briefly claimed the imperial title in Gaul during the early 5th century Western Roman Empire.
-
E.
Aurelian
Aurelian was a 3rd-century Roman emperor known for restoring the empire’s unity and strengthening its frontiers through military reforms and administrative reorganization.
- 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_69d8278a06e481908b5d6af0a8afe737 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6213801c8190a47705cd890b9ae7 |
completed | April 14, 2026, 3:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd324f501081908f7017302bc40b3a |
completed | May 8, 2026, 12:46 a.m. |
Created at: April 10, 2026, 1:06 a.m.