Triple

T8821470
Position Surface form Disambiguated ID Type / Status
Subject Michael Baca E209912 entity
Predicate caseOutcomeForElectorDiscretion P84818 FINISHED
Object Supreme Court held states may bind electors 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: Supreme Court held states may bind electors | Statement: [Michael Baca, caseOutcomeForElectorDiscretion, Supreme Court held states may bind electors]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: caseOutcomeForElectorDiscretion
Context triple: [Michael Baca, caseOutcomeForElectorDiscretion, Supreme Court held states may bind electors]
  • A. caseDecidedBy
    Indicates that a legal case is resolved or adjudicated by a specific decision-making authority, such as a judge or court.
  • B. councilOutcome
    Indicates the result or decision produced by a council after its deliberation or proceedings.
  • C. decisionResultsIn
    Indicates that a particular decision leads to, causes, or brings about a specific outcome or result.
  • D. decidesOn
    Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
  • E. wasDecidedBy
    Indicates that a decision or outcome was determined or resolved by a specific agent or authority.
  • 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_69ca8364e13081909c85fe80f44fe86f completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc601126248190b6f10c22f1aeac9a completed April 1, 2026, midnight
PD Predicate disambiguation batch_69cc5c21e64c81908490e3b0875dc0d6 completed March 31, 2026, 11:43 p.m.
PDg Predicate description generation batch_69cc5cff3608819081d2d7e5c16d44b7 completed March 31, 2026, 11:47 p.m.
Created at: March 30, 2026, 6:46 p.m.