Triple

T14478862
Position Surface form Disambiguated ID Type / Status
Subject Federal Rule of Evidence 807 E359047 entity
Predicate isResidualException P114349 FINISHED
Object true 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: true | Statement: [Federal Rule of Evidence 807, isResidualException, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isResidualException
Context triple: [Federal Rule of Evidence 807, isResidualException, true]
  • A. hasExceptionFor
    Indicates that a general rule, condition, or behavior does not apply in a particular case or under specific circumstances.
  • B. includesException
    Indicates that one entity explicitly contains, references, or accounts for a specified exception within its definition, behavior, or processing.
  • C. hasException
    Indicates that a general rule, process, or condition does not apply in a particular case due to a specified exception.
  • D. hasExceptionConstruct
    Indicates that a construct or element is associated with, or defined by, a specific exception-handling construct (such as a try-catch or similar exception mechanism).
  • E. isRootExceptionClassIn
    Indicates that a given exception class serves as the root (top-level) exception within a specified exception hierarchy or context.
  • 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_69d827966698819082e140837737501d completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de924a576c819098351efabdb779b1 completed April 14, 2026, 7:15 p.m.
PD Predicate disambiguation batch_69de5c487b4c819097803e58dca628a5 completed April 14, 2026, 3:24 p.m.
PDg Predicate description generation batch_69de5fb4de14819092acdecbd201d672 completed April 14, 2026, 3:39 p.m.
Created at: April 10, 2026, 1:20 a.m.