Triple
T31735735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan Proposal 2 (2006) |
E809987
|
entity |
| Predicate | voterInitiated |
P172897
|
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: [Michigan Proposal 2 (2006), voterInitiated, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voterInitiated Context triple: [Michigan Proposal 2 (2006), voterInitiated, true]
-
A.
votingIs
Indicates that an entity is engaged in, characterized by, or involved in the act or process of voting.
-
B.
voterApproval
Indicates that a voter has given consent, support, or positive endorsement to a proposal, candidate, or decision.
-
C.
votingStatus
Indicates whether an entity is currently eligible, registered, or has participated in a voting process.
-
D.
usesVoterRegistration
Indicates that one entity relies on or applies another entity’s voter registration information for a particular purpose or process.
-
E.
voted
Indicates that an entity formally expressed a choice or decision, typically in an election, poll, or decision-making process, regarding another entity or option.
- 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 30, 2026, 11:23 p.m.