Triple

T71826
Position Surface form Disambiguated ID Type / Status
Subject California term limits law E1436 entity
Predicate intendedEffect P812 FINISHED
Object increase legislative turnover 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: increase legislative turnover | Statement: [California term limits law, intendedEffect, increase legislative turnover]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: intendedEffect
Context triple: [California term limits law, intendedEffect, increase legislative turnover]
  • A. primaryEffect
    Indicates the main direct outcome or consequence that results from a given cause, action, or condition.
  • B. hasConsequence chosen
    Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
  • C. purpose
    Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
  • D. designedToEvoke
    Indicates that something was intentionally created or arranged in order to elicit a particular reaction, feeling, or response from an audience or observer.
  • E. influenced
    Indicates that one entity has affected, shaped, or altered another entity’s state, behavior, or characteristics.
  • 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_69a24c06b3bc8190aa4ac89026115efc completed Feb. 28, 2026, 1:59 a.m.
NER Named-entity recognition batch_69a24f6997c081908b202f937eb2b14f completed Feb. 28, 2026, 2:14 a.m.
PD Predicate disambiguation batch_69a24eab7f408190a8275cb82474f575 completed Feb. 28, 2026, 2:10 a.m.
Created at: Feb. 28, 2026, 2:03 a.m.