Triple
T16763037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Proposition 215 |
E407391
|
entity |
| Predicate | campaignOpponents |
P124543
|
FINISHED |
| Object | many law enforcement organizations |
—
|
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: many law enforcement organizations | Statement: [California Proposition 215, campaignOpponents, many law enforcement organizations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campaignOpponents Context triple: [California Proposition 215, campaignOpponents, many law enforcement organizations]
-
A.
opponentCampaign
Indicates a relationship where one campaign is positioned as competing against or opposing another campaign.
-
B.
electionOpponent
Indicates that two individuals are rivals competing against each other in the same election.
-
C.
opponentCandidate
Indicates that one entity is a rival or competing candidate against another in the same contest or election.
-
D.
incumbentOpponent
Indicates that one entity is the current officeholder while the other is their electoral challenger for that same position.
-
E.
mainOpposingPolitician
Indicates that one politician is the primary political rival or adversary of another.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3abee862c819086d9bf01e623a8ce |
completed | April 18, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326bac94481908c082117553320f8 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:21 a.m.