Triple
T6144841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2007 Chicago mayoral election |
E137049
|
entity |
| Predicate | resultForIncumbent |
P6364
|
FINISHED |
| Object | reelected |
—
|
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: reelected | Statement: [2007 Chicago mayoral election, resultForIncumbent, reelected]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultForIncumbent Context triple: [2007 Chicago mayoral election, resultForIncumbent, reelected]
-
A.
incumbentAfterElection
Indicates that an entity holds a position or office as the sitting incumbent following a specified election.
-
B.
incumbent
Indicates that an entity currently holds a particular position, office, or role at the present time.
-
C.
incumbentBeforeElection
chosen
Indicates that the subject was already holding the relevant office or position prior to the specified election.
-
D.
lastIncumbent
Indicates that the subject is the most recent person or entity to have held a particular position, office, or role before the current one.
-
E.
featuredIncumbentGovernorRunning
Indicates that the highlighted or primary subject is the current sitting governor who is running for election or re-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_69c008a2c6308190a56519b22d55d083 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05cb645508190aea2d77c9de174ba |
completed | March 22, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69c055f39e0881909ae56444b1b48929 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:16 p.m.