Triple
T14588408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vespasia |
E342378
|
entity |
| Predicate | derivesFrom |
P909
|
FINISHED |
| Object | Vespasius |
E1112437
|
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: Vespasius | Statement: [Vespasia, derivesFrom, Vespasius]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vespasius Context triple: [Vespasia, derivesFrom, Vespasius]
-
A.
Vespasius
chosen
Vespasius is the Latin nomen (family name) of the ancient Roman Vespasii family, from which the emperor Vespasian descended.
-
B.
Quintus Marcius Rex
Quintus Marcius Rex was a Roman statesman and magistrate best known for overseeing major public works, including the construction of important aqueduct infrastructure in ancient Rome.
-
C.
Gnaeus Domitius Ahenobarbus
Gnaeus Domitius Ahenobarbus was a Roman senator and aristocrat of the Julio-Claudian dynasty, best known as the biological father of the emperor Nero.
-
D.
Ianus Bifrons
Ianus Bifrons is a title of the Roman god Janus emphasizing his two-faced aspect, symbolizing his role as guardian of transitions, beginnings, and endings.
-
E.
Caius
Caius is the Latinized name of Sir Kay, the legendary knight of King Arthur’s court in Arthurian mythology.
- 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4237d88819097f3f9a40f5be152 |
completed | April 14, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fde169eb6481909d7fac6d984a2af1 |
completed | May 8, 2026, 1:13 p.m. |
Created at: April 10, 2026, 1:24 a.m.