Triple
T9650206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bailey Olter |
E233310
|
entity |
| Predicate | causeOfLeavingOffice |
P15987
|
FINISHED |
| Object | ill health |
—
|
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: ill health | Statement: [Bailey Olter, causeOfLeavingOffice, ill health]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfLeavingOffice Context triple: [Bailey Olter, causeOfLeavingOffice, ill health]
-
A.
causeOfEndOfPresidency
Indicates the event, action, or circumstance that directly led to the termination of a person’s presidency.
-
B.
afterLeavingOffice
Indicates that one event, action, or state occurs subsequent to an entity’s departure from an official position or office.
-
C.
reasonForLeaving
chosen
Indicates the cause, motivation, or circumstance that led an entity to depart or discontinue an association, position, or place.
-
D.
reasonForAbdication
Indicates the specific cause, motive, or circumstances that led an individual to formally abdicate a position of authority or power.
-
E.
succeedsFromOffice
Indicates that one officeholder directly follows another in holding the same office or 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_69ca848b31648190b57aa55da20285be |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9badd630819087fd844d7878ec61 |
completed | April 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b0263081908cf6df3eb07d71b0 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:13 p.m.