Triple
T7706129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1922 California gubernatorial election |
E174620
|
entity |
| Predicate | isStatewide |
P78404
|
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: [1922 California gubernatorial election, isStatewide, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStatewide Context triple: [1922 California gubernatorial election, isStatewide, true]
-
A.
usedByStateOrTerritory
Indicates that something (such as an object, system, or resource) is utilized or employed by a specific state or territory.
-
B.
regionalLocationWithinState
Indicates that one region is geographically located within the boundaries of a specific state.
-
C.
isRegionalJurisdictionOf
Indicates that one entity functions as the governing or administrative authority over a specific geographic region or area.
-
D.
conventionState
Indicates that an entity is in a particular formal status or phase within a convention or agreed procedural framework.
-
E.
servesStateOrDistrict
Indicates that an entity holds a role or position in service to a specific state or electoral district.
- 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_69c6995b3e8c8190833108f883d5f53c |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c70165e78c8190bf6b3c34e243cb81 |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c7040091608190a9e46ecfb2ff0bca |
completed | March 27, 2026, 10:26 p.m. |
Created at: March 27, 2026, 4:03 p.m.