Triple

T26675298
Position Surface form Disambiguated ID Type / Status
Subject Temporary Protected Status E672438 entity
Predicate consequenceOfTermination P165049 FINISHED
Object loss of TPS-based work authorization 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: loss of TPS-based work authorization | Statement: [Temporary Protected Status, consequenceOfTermination, loss of TPS-based work authorization]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: consequenceOfTermination
Context triple: [Temporary Protected Status, consequenceOfTermination, loss of TPS-based work authorization]
  • A. consequenceOfRevocation
    Indicates that something occurs as a direct result of a prior revocation event or decision.
  • B. natureOfTermination
    Indicates the manner, cause, or conditions under which a relationship, contract, or employment is brought to an end.
  • C. consequenceOfExpiry
    Indicates that something occurs as a direct result of an expiry event or the state of having expired.
  • D. typicallyTerminatedIn
    Indicates that an event, process, or state usually ends or concludes in a particular way or outcome.
  • E. consequenceOfApplication
    Indicates that something occurs as a result or outcome of a particular application or use of something.
  • 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_69eecda13424819092b17942c4edf722 completed April 27, 2026, 2:44 a.m.
NER Named-entity recognition batch_69f65705a3048190a3728b695ba2ae65 completed May 2, 2026, 7:56 p.m.
PD Predicate disambiguation batch_69f651a731508190bb0c8c2462eba224 completed May 2, 2026, 7:33 p.m.
PDg Predicate description generation batch_69f6562ef4e4819082ce6abd41b74dc5 completed May 2, 2026, 7:53 p.m.
Created at: April 27, 2026, 3:16 a.m.