Triple
T2966482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galba |
E80176
|
entity |
| Predicate | predecessor |
P97
|
FINISHED |
| Object | Nero |
E12097
|
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: Nero | Statement: [Galba, predecessor, Nero]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nero Context triple: [Galba, predecessor, Nero]
-
A.
Nero
chosen
Nero was a 1st-century Roman emperor best known for his tyrannical rule, persecution of Christians, and association with the Great Fire of Rome.
-
B.
Nero
Nero is the vengeful Romulan miner who serves as the primary antagonist in the 2009 Star Trek film reboot.
-
C.
Caligula
Caligula was a first-century Roman emperor infamous for his autocratic rule, extravagance, and accounts of cruelty and madness.
-
D.
Galba
Galba was a Roman general and statesman who briefly ruled as emperor during the tumultuous Year of the Four Emperors following Nero’s death.
-
E.
Elagabalus
Elagabalus was a Roman emperor of the Severan dynasty known for his short, tumultuous reign and controversial religious and social reforms.
- 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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad996e93788190ba9883714d4dfa0c |
completed | March 8, 2026, 3:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b20f38a1548190bdddf65853632db1 |
completed | March 12, 2026, 12:56 a.m. |
Created at: March 8, 2026, 2:58 p.m.