Triple

T35513854
Position Surface form Disambiguated ID Type / Status
Subject Humberto Munoz-Flores E1026357 entity
Predicate caseHeWasIn_decidedBy P97352 FINISHED
Object Supreme Court of the United States NE NERFINISHED

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 of the United States | Statement: [Humberto Munoz-Flores, caseHeWasIn_decidedBy, Supreme Court of the United States]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: caseHeWasIn_decidedBy
Context triple: [Humberto Munoz-Flores, caseHeWasIn_decidedBy, Supreme Court of the United States]
  • A. caseDecidedBy
    Indicates that a legal case is resolved or adjudicated by a specific decision-making authority, such as a judge or court.
  • B. caseDecidedIn
    Indicates that a particular legal case was resolved or adjudicated within a specified court, jurisdiction, or decision-making body.
  • C. wasDecidedBy
    Indicates that a decision or outcome was determined or resolved by a specific agent or authority.
  • D. decidedIn
    Indicates that a decision, ruling, or outcome was made within a particular case, proceeding, or deliberative context.
  • E. legalCaseHeParticipatedInDecidedBy chosen
    Indicates that a legal case in which he participated was decided or adjudicated by a specified authority or court.
  • 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_69f76dfd61208190b93ec6dc439cab41 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79a54aa3c8190b2bb5d790b2d42d4 completed May 3, 2026, 6:56 p.m.
PD Predicate disambiguation batch_69f7961970408190b669cc556e30a608 completed May 3, 2026, 6:38 p.m.
Created at: May 3, 2026, 4:04 p.m.