Triple
T518337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caligula |
E10757
|
entity |
| Predicate | predecessor |
P97
|
FINISHED |
| Object | Tiberius |
E9795
|
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: Tiberius | Statement: [Caligula, predecessor, Tiberius]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tiberius Context triple: [Caligula, predecessor, Tiberius]
-
A.
Tiberius
chosen
Tiberius was the second Roman emperor, ruling from AD 14 to 37, known for his capable early administration and later reclusive, often harsh governance.
-
B.
Vespasian
Vespasian was a 1st-century Roman emperor best known for restoring stability after Nero’s reign and initiating major building projects such as the Colosseum.
-
C.
Claudius
Claudius is a masculine given name of ancient Roman origin, famously borne by several Roman emperors and historical figures.
-
D.
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.
-
E.
Claudiianus
Claudiianus is a Latin-derived personal name likely associated with or stemming from the Roman family name Claudius.
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f19ee6748190916603ef3a9e27f3 |
completed | Feb. 28, 2026, 1:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a4e9b6d1088190a925b1b3d78e9674 |
completed | March 2, 2026, 1:36 a.m. |
Created at: Feb. 28, 2026, 1:12 p.m.