Triple
T33252910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Kirkman |
E851296
|
entity |
| Predicate | successorAsPresidentInSeries |
P10458
|
FINISHED |
| Object | Cornelius Moss |
—
|
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: Cornelius Moss | Statement: [Tom Kirkman, successorAsPresidentInSeries, Cornelius Moss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsPresidentInSeries Context triple: [Tom Kirkman, successorAsPresidentInSeries, Cornelius Moss]
-
A.
precedesInSuccessionToPresidency
Indicates that one individual held the presidency immediately before another, establishing a direct order in presidential succession.
-
B.
succeededByAsPresident
chosen
Indicates that one individual directly followed another in holding the office of president.
-
C.
followedByPresidencyOf
Indicates that one presidency directly succeeds another in chronological order.
-
D.
successorInauguralSeason
Indicates that one season is the immediate next inaugural season following another season in a sequence.
-
E.
precededAsVicePresidentBy
Indicates that one entity served as vice president immediately before another entity in a sequence of officeholders.
- 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_69f34963135c819084e7f1d483421f00 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff878f41888190bcb3bc41ad26081a |
completed | May 9, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69ff854082d88190aad3bfedf05e849f |
completed | May 9, 2026, 7:04 p.m. |
Created at: May 1, 2026, 1:31 a.m.