Triple
T33254764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bob Dole presidential campaign |
E851345
|
entity |
| Predicate | incumbentOpponentOffice |
P9225
|
FINISHED |
| Object | President of the United States |
—
|
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: President of the United States | Statement: [Bob Dole presidential campaign, incumbentOpponentOffice, President of the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incumbentOpponentOffice Context triple: [Bob Dole presidential campaign, incumbentOpponentOffice, President of the United States]
-
A.
incumbentOpponent
chosen
Indicates that one entity is the current officeholder while the other is their electoral challenger for that same position.
-
B.
incumbentPosition
Indicates that a person currently holds or occupies a specific position, office, or role.
-
C.
electionOpponent
Indicates that two individuals are rivals competing against each other in the same election.
-
D.
incumbentOffice
Indicates that a person currently holds and serves in a specified office or position.
-
E.
electedOffice
Indicates that an entity holds or has held a particular office or position as a result of an election.
- 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_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:31 a.m.