Triple
T17304795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California politics |
E420132
|
entity |
| Predicate | hasVotingExpansion |
P126911
|
FINISHED |
| Object | motor voter registration |
—
|
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: motor voter registration | Statement: [California politics, hasVotingExpansion, motor voter registration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVotingExpansion Context triple: [California politics, hasVotingExpansion, motor voter registration]
-
A.
hasExpansionSetNumber
Indicates that an entity is associated with a specific numbered position or identifier within an expansion set.
-
B.
hasExpansion
Indicates that one entity serves as a larger, extended, or elaborated form of another entity.
-
C.
hasVotingPower
Indicates that an entity possesses the authority or capacity to participate in a decision-making or electoral process by casting votes.
-
D.
hasVotingPlatform
Indicates that an entity is associated with or utilizes a particular platform or system for conducting voting or elections.
-
E.
usesVotingBallots
Indicates that one entity conducts or participates in a voting process by employing ballots as the method for casting votes.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e438fe1d408190a429d1dba50d0c58 |
completed | April 19, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:41 a.m.