Triple

T17480055
Position Surface form Disambiguated ID Type / Status
Subject Payton v. New York E425631 entity
Predicate exceptionRecognized P28876 FINISHED
Object exigent circumstances exception to the warrant requirement 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: exigent circumstances exception to the warrant requirement | Statement: [Payton v. New York, exceptionRecognized, exigent circumstances exception to the warrant requirement]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: exceptionRecognized
Context triple: [Payton v. New York, exceptionRecognized, exigent circumstances exception to the warrant requirement]
  • A. exception
    Indicates that a particular case does not follow the usual rule, pattern, or condition that applies to others.
  • B. notableException
    Indicates that something or someone stands out as an unusual or noteworthy deviation from an expected pattern, rule, or general case.
  • C. reasonForException chosen
    Indicates the specific cause or justification for why a normal rule, process, or condition does not apply in a given case.
  • D. errorRecovery
    Indicates that an entity detects a failure or error condition and initiates actions to restore normal or acceptable operation.
  • E. notRecognizedBy
    Indicates that one entity does not acknowledge, accept, or formally recognize the status, authority, or validity of another entity.
  • 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_69d889dbc2e88190b18ea6115e819258 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e451bf1e8081909f4d4b8992412e62 completed April 19, 2026, 3:53 a.m.
PD Predicate disambiguation batch_69e3b4f341c88190adabe526d8903b05 completed April 18, 2026, 4:44 p.m.
Created at: April 10, 2026, 5:48 a.m.