Triple
T28531295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Proposition 6 (1978) |
E722048
|
entity |
| Predicate | wasOnBallotIn |
P164613
|
FINISHED |
| Object | 1978 California state election |
—
|
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: 1978 California state election | Statement: [California Proposition 6 (1978), wasOnBallotIn, 1978 California state election]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasOnBallotIn Context triple: [California Proposition 6 (1978), wasOnBallotIn, 1978 California state election]
-
A.
wasCandidateIn
Indicates that an entity served as a candidate in a particular election, contest, or selection process.
-
B.
hasBallotAccessFor
Indicates that an entity is permitted or qualified to appear on the ballot for a particular election or jurisdiction.
-
C.
usedInElection
Indicates that something (such as a resource, tool, or method) was employed or applied as part of conducting an election.
-
D.
firstBallotCandidate
Indicates that the entity was a candidate in the first ballot of an election or selection process.
-
E.
hasElectoralVoteIn
Indicates that an entity possesses or receives electoral votes within a specified election or jurisdiction.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64fd617588190904f94042d6f3eb1 |
completed | May 2, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 28, 2026, 3:28 a.m.