Triple
T38667486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2009 Seattle mayoral election |
E940491
|
entity |
| Predicate | runoffCandidate |
P191499
|
FINISHED |
| Object | Mike McGinn |
—
|
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: Mike McGinn | Statement: [2009 Seattle mayoral election, runoffCandidate, Mike McGinn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runoffCandidate Context triple: [2009 Seattle mayoral election, runoffCandidate, Mike McGinn]
-
A.
runnerUp
Indicates that one entity finished in second place relative to another in a competition or ranking.
-
B.
candidateFor
Indicates that one entity is being considered or proposed as a possible choice, option, or selection for another entity (such as a role, position, or outcome).
-
C.
featuredCandidate
Indicates that a particular candidate is highlighted or given special prominence relative to others.
-
D.
numberOfRunoffCandidates
Indicates the count of candidates who advance to or participate in a runoff election.
-
E.
runnerUpPoliticalPosition
Indicates that an entity finished in second place (runner-up) in a specified political position or election for that position.
- 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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdfbafbf48190abe38ec0003a6419 |
completed | May 7, 2026, 6:53 p.m. |
Created at: May 3, 2026, 4:33 p.m.