Triple

T434523
Position Surface form Disambiguated ID Type / Status
Subject United States Court of Appeals for the First Circuit E9782 entity
Predicate mayHear P13933 FINISHED
Object interlocutory appeals in certain circumstances 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: interlocutory appeals in certain circumstances | Statement: [United States Court of Appeals for the First Circuit, mayHear, interlocutory appeals in certain circumstances]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mayHear
Context triple: [United States Court of Appeals for the First Circuit, mayHear, interlocutory appeals in certain circumstances]
  • A. hears
    Indicates that one entity perceives or detects sounds produced by another entity or source.
  • B. mayMeet
    Indicates that one entity is permitted or has the possibility to meet or come together with another entity.
  • C. mayHold
    Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
  • D. mayReportTo
    Indicates that one entity is permitted or allowed to have a reporting relationship to another entity, such as an employee being allowed to report to a particular manager.
  • E. mayResultIn
    Indicates that one entity has the potential to cause, lead to, or bring about another entity or outcome, without guaranteeing that it will occur.
  • 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_69a2e801e1d48190b505d1dd336b52ac completed Feb. 28, 2026, 1:05 p.m.
NER Named-entity recognition batch_69a2ef0a008c8190ae0aa25e4df9c35f completed Feb. 28, 2026, 1:35 p.m.
PD Predicate disambiguation batch_69a2edda55e88190b7c17ba94d7df1ce completed Feb. 28, 2026, 1:30 p.m.
PDg Predicate description generation batch_69a2eeb93584819082f23eff13e17c4f completed Feb. 28, 2026, 1:33 p.m.
Created at: Feb. 28, 2026, 1:11 p.m.