Triple
T26081367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iowa Democratic caucuses 1996 |
E657852
|
entity |
| Predicate | hasIncumbentAdvantage |
P180590
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Iowa Democratic caucuses 1996, hasIncumbentAdvantage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIncumbentAdvantage Context triple: [Iowa Democratic caucuses 1996, hasIncumbentAdvantage, true]
-
A.
backedIncumbent
Indicates that a person or organization provided support to the current officeholder or existing position-holder, typically in a political or competitive context.
-
B.
hasHadIncumbent
Indicates that an entity has previously served as the incumbent (current holder) of a particular position or role.
-
C.
incumbentOutcome
Indicates the result or consequence experienced by the current officeholder or position-holder in a given event or context.
-
D.
incumbent
Indicates that an entity currently holds a particular position, office, or role at the present time.
-
E.
incumbentBeforeElection
Indicates that the subject was already holding the relevant office or position prior to the specified election.
- F. None of above. chosen
Provenance (4 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f74654c09c819084879162eba9d641 |
completed | May 3, 2026, 12:57 p.m. |
Created at: April 26, 2026, 7:38 p.m.