Triple
T17403732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balbinus |
E423159
|
entity |
| Predicate | coRulerWith |
P13111
|
FINISHED |
| Object | Pupienus |
—
|
NE NERFINISHED |
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: Pupienus | Statement: [Balbinus, coRulerWith, Pupienus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pupienus Context triple: [Balbinus, coRulerWith, Pupienus]
-
A.
Pupienus
chosen
Pupienus was a briefly reigning Roman emperor in 238 AD, known for his joint rule with Balbinus during the turbulent Year of the Six Emperors.
-
B.
Papius
Papius was an ancient Roman family name (nomen gentilicium) associated with members of the Papii gens, including the politician Gaius Papius Mutilus.
-
C.
Lollius
Lollius was the Roman gens (family line) to which the aristocratic woman and briefly reigning empress Lollia Paulina belonged.
-
D.
Sabinus
Sabinus is a cognomen used by members of the ancient Roman Claudian gens, identifying a particular family branch within this prominent patrician lineage.
-
E.
Sabinianus
Sabinianus was the birth name of Pope Sabinian, a 7th-century bishop of Rome who succeeded Pope Gregory I.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43b051cc48190872278ee0b52240d |
completed | April 19, 2026, 2:16 a.m. |
Created at: April 10, 2026, 5:45 a.m.