Triple
T21013915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proposition 1A (2008) |
E517619
|
entity |
| Predicate | ballotLocation |
P110737
|
FINISHED |
| Object | California general election ballot |
—
|
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: California general election ballot | Statement: [Proposition 1A (2008), ballotLocation, California general election ballot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballotLocation Context triple: [Proposition 1A (2008), ballotLocation, California general election ballot]
-
A.
ballot
Indicates that an entity participates in a formal voting process, typically by casting or submitting a vote or choice.
-
B.
ballotNumber
Indicates the specific numerical identifier assigned to a ballot within an election or voting process.
-
C.
locationOfPolling
chosen
Indicates the place where a polling or voting event is held or conducted.
-
D.
ballotUnitUsed
Indicates that a particular ballot unit was utilized in the conduct of an election or voting process.
-
E.
positionOnBallot
Indicates the specific ordered place that a candidate or option occupies on an election ballot.
- 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_69e0b50192308190a284fcc89dd23a49 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc5764188190829de6f5abd6e00f |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:54 p.m.