Triple

T19318693
Position Surface form Disambiguated ID Type / Status
Subject Los Angeles municipal elections E483162 entity
Predicate ballotMeasuresIncluded P132386 FINISHED
Object yes 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: yes | Statement: [Los Angeles municipal elections, ballotMeasuresIncluded, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ballotMeasuresIncluded
Context triple: [Los Angeles municipal elections, ballotMeasuresIncluded, yes]
  • A. ballotsInclude chosen
    Indicates that a given set of ballots contains or records the specified option, candidate, or choice.
  • B. ballotMeasureNumber
    Indicates the specific identifying number assigned to a ballot measure within an election or voting context.
  • C. ballotAccessRegulatedBy
    Indicates that the rules or conditions for appearing on an election ballot are controlled, governed, or determined by a particular authority or regulation.
  • D. includesElectionsIn
    Indicates that one entity (such as a document, dataset, or process) encompasses, covers, or contains elections that occur within the scope or domain of another entity.
  • E. ballot
    Indicates that an entity participates in a formal voting process, typically by casting or submitting a vote or choice.
  • 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_69d8e8d13e3c81909d91d1d5ec37c095 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e60d868dd48190b1439a5f4ff58c48 completed April 20, 2026, 11:27 a.m.
PD Predicate disambiguation batch_69e4dd0ef66881909d489d634eee817a completed April 19, 2026, 1:47 p.m.
Created at: April 10, 2026, 1:32 p.m.