Triple

T35129594
Position Surface form Disambiguated ID Type / Status
Subject Rule 35 – Summary Judgments E1014400 entity
Predicate consequenceOfImproperGrant P150475 FINISHED
Object reversible error on appeal 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: reversible error on appeal | Statement: [Rule 35 – Summary Judgments, consequenceOfImproperGrant, reversible error on appeal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: consequenceOfImproperGrant
Context triple: [Rule 35 – Summary Judgments, consequenceOfImproperGrant, reversible error on appeal]
  • A. consequenceOfRevocation
    Indicates that something occurs as a direct result of a prior revocation event or decision.
  • B. cannotGrant
    Indicates that an entity lacks the authority, permission, or ability to confer a requested right, access, or resource to another entity.
  • C. consequenceOfApplication
    Indicates that something occurs as a result or outcome of a particular application or use of something.
  • D. unexpectedConsequenceOf chosen
    Indicates that one event, action, or condition occurs as an unforeseen or unintended result of another.
  • E. notAutomaticallyGranted
    Indicates that the specified right, status, or permission is not given by default and requires an explicit action or approval to be obtained.
  • 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_69f76dd9c1848190af70d4882a2c1ad7 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fb2e940d5c8190bceae77daf4ef512 completed May 6, 2026, 12:05 p.m.
PD Predicate disambiguation batch_69f9fec70bd881909c658a3c5020318b completed May 5, 2026, 2:29 p.m.
Created at: May 3, 2026, 4:02 p.m.