Triple

T29913729
Position Surface form Disambiguated ID Type / Status
Subject McPherson v. Blacker E759736 entity
Predicate natureOfDecision P2165 FINISHED
Object constitutional interpretation of Article II 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: constitutional interpretation of Article II | Statement: [McPherson v. Blacker, natureOfDecision, constitutional interpretation of Article II]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: natureOfDecision
Context triple: [McPherson v. Blacker, natureOfDecision, constitutional interpretation of Article II]
  • A. decisionType chosen
    Indicates the specific category or nature of a decision associated with an entity or event.
  • B. knownForDecision
    Indicates that an entity is recognized or notable specifically for making a particular decision.
  • C. decisionDirection
    Indicates the orientation or course (e.g., choice, stance, or path) that a decision takes relative to available options or influencing factors.
  • D. decisionMaking
    Indicates the process by which an entity evaluates options and selects a course of action among alternatives.
  • E. decisionsAre
    Indicates that certain choices, judgments, or resolutions possess a specified quality, status, or classification.
  • 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_69f2246189fc8190996b63ee1f9a2374 completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f697eabb048190bc01a830f14942c6 completed May 3, 2026, 12:33 a.m.
PD Predicate disambiguation batch_69f69664142c8190bc695501056b0236 completed May 3, 2026, 12:27 a.m.
Created at: April 29, 2026, 6:11 p.m.