Triple
T16452294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pupienus |
E399581
|
entity |
| Predicate | removedFromOfficeIn |
P3900
|
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, removedFromOfficeIn, 238]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: removedFromOfficeIn Context triple: [Pupienus, removedFromOfficeIn, 238]
-
A.
removedFrom
Indicates that one entity has been taken away, extracted, or detached from another entity or context.
-
B.
removedFromPublicDuties
Indicates that an entity has been taken out of roles or responsibilities that involve serving or representing the public.
-
C.
separatedFromOffice
chosen
Indicates that an individual has been removed or dismissed from holding a particular office or official position.
-
D.
removedOn
Indicates that an entity was taken away, deleted, or detached at a specific point in time.
-
E.
removedOfficialStatusFrom
Indicates that one entity revoked or took away the official status or position previously held by another entity.
- 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.