Triple
T16452293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pupienus |
E399581
|
entity |
| Predicate | officeAssumedIn |
P88506
|
FINISHED |
| Object | 238 |
—
|
LITERAL 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: 238 | Statement: [Pupienus, officeAssumedIn, 238]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeAssumedIn Context triple: [Pupienus, officeAssumedIn, 238]
-
A.
officeAssumedFrom
Indicates that one party has taken over or begun holding an office or position previously held by another party.
-
B.
officeAssumedAt
chosen
Indicates the time or event at which an individual formally begins holding a particular office or position.
-
C.
officeAssumedAfter
Indicates that one entity began holding an office or position after another entity had already assumed that same office.
-
D.
officeAssumedInSeries
Indicates that an office or position is assumed as part of a sequential series of office-holdings or terms.
-
E.
officeAssumedByCurrentRepresentative
Indicates that the office in question is currently held by the representative who has assumed that position.
- F. None of above.
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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32ce19344819083d323077b742bc3 |
completed | April 18, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.