Triple
T435183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiberius |
E9795
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | Caligula |
E10757
|
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: Caligula | Statement: [Tiberius, successor, Caligula]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Caligula Context triple: [Tiberius, successor, Caligula]
-
A.
Caligula
chosen
Caligula was a first-century Roman emperor infamous for his autocratic rule, extravagance, and accounts of cruelty and madness.
-
B.
Nero
Nero was a 1st-century Roman emperor best known for his tyrannical rule, persecution of Christians, and association with the Great Fire of Rome.
-
C.
Commodus
Commodus was a Roman emperor (reigned 180–192 AD) known for his erratic rule, self-indulgence, and association with the decline of the Roman Empire.
-
D.
Claudiianus
Claudiianus is a Latin-derived personal name likely associated with or stemming from the Roman family name Claudius.
-
E.
Claudius Pompeianus
Claudius Pompeianus was a prominent 2nd-century Roman general and senator, son-in-law of Emperor Marcus Aurelius, who played a key military role during the Marcomannic Wars.
- 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ef0b6e0c8190ad6a335ee804829c |
completed | Feb. 28, 2026, 1:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a4a424e0d88190b0ad5d0827b762ae |
completed | March 1, 2026, 8:40 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.