Triple
T34971058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arizona statewide elections |
E1008537
|
entity |
| Predicate | includesStateOffices |
P206774
|
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: [Arizona statewide elections, includesStateOffices, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesStateOffices Context triple: [Arizona statewide elections, includesStateOffices, true]
-
A.
politicalOfficeJurisdiction
Indicates the governmental area or jurisdiction over which a political office holds authority or responsibility.
-
B.
hasBoardOffices
Indicates that an organization maintains official board offices or board-level administrative locations.
-
C.
stateLevelOfficeHeld
Indicates that an entity has held a public office or position within a state-level government.
-
D.
positionOnStateGovernment
Indicates that an entity holds an official role or seat within a state-level government.
-
E.
governmentOffices
Indicates that one entity is a government office or administrative agency associated with, located in, or serving the other entity.
- 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_69f76dc78a308190a1ac29ad4a9a4895 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:01 p.m.