Triple
T3022526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1998 California gubernatorial election |
E82494
|
entity |
| Predicate | wasStatewide |
P14577
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [1998 California gubernatorial election, wasStatewide, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasStatewide Context triple: [1998 California gubernatorial election, wasStatewide, yes]
-
A.
tookPlaceInState
chosen
Indicates that an event or occurrence happened within the geographical or political boundaries of a specific state.
-
B.
affectedU.S.State
Indicates that a particular U.S. state is impacted or influenced by a specified event, condition, or entity.
-
C.
majorState
Indicates that a state holds significant power, influence, or importance relative to other states within a given system or context.
-
D.
consideredByMostStatesAs
Indicates that something is regarded or classified in a particular way by the majority of states or countries.
-
E.
representedState
Indicates that one entity serves as a representation or depiction of the state or condition of another entity.
- 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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a963034819093d96566e9b0cea9 |
completed | March 8, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69ad961c430c8190ac48f2e3c7e7c649 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.