Triple
T26674979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George H. W. Bush–Dan Quayle ticket |
E672432
|
entity |
| Predicate | presidentialNomineeNumberAsPresident |
P2349
|
FINISHED |
| Object | 41 |
—
|
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: 41 | Statement: [George H. W. Bush–Dan Quayle ticket, presidentialNomineeNumberAsPresident, 41]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presidentialNomineeNumberAsPresident Context triple: [George H. W. Bush–Dan Quayle ticket, presidentialNomineeNumberAsPresident, 41]
-
A.
presidentNumberElected
Indicates the ordinal number corresponding to the sequence in which a person was elected president.
-
B.
incumbentPresidentNumber
Indicates the ordinal position or sequence number of the person currently serving as president.
-
C.
presidentialNumber
chosen
Indicates the ordinal position a person holds in a sequence of presidents (e.g., first, second, third president).
-
D.
designationAsPresidentWas
Indicates that an entity was formally appointed or recognized as president of another entity at a particular time or under specific conditions.
-
E.
termCountAsPresident
Indicates the number of terms an individual has served in the role of president.
- 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_69eecda13424819092b17942c4edf722 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 3:15 a.m.