Triple

T5261555
Position Surface form Disambiguated ID Type / Status
Subject Varig E118834 entity
Predicate enteredJudicialRecovery P62607 FINISHED
Object 2005 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: 2005 | Statement: [Varig, enteredJudicialRecovery, 2005]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: enteredJudicialRecovery
Context triple: [Varig, enteredJudicialRecovery, 2005]
  • A. enteredConservatorship
    Indicates that an entity has been placed under a legal conservatorship, where another party is granted authority to manage its personal or financial affairs.
  • B. recoveredIn
    Indicates that something lost, damaged, or impaired has been restored or regained within a particular context, process, or location.
  • C. recoveredFrom
    Indicates that an entity has returned to a normal or improved state after previously experiencing or being affected by another specified condition, event, or problem.
  • D. laterCourt
    Indicates that one court decision or proceeding occurs at a later time than another court decision or proceeding.
  • E. rehabilitatedBy
    Indicates that an entity has been restored, treated, or brought back to a better or functional state through the actions or intervention of another entity.
  • 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_69bd446a42c88190b7ecbef006561d55 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd7bd0c5f48190a1be89314c59f96b completed March 20, 2026, 4:54 p.m.
PD Predicate disambiguation batch_69bd77c55224819096c0bcfcfae79bd3 completed March 20, 2026, 4:37 p.m.
PDg Predicate description generation batch_69bd7bcabe58819096255672664513b1 completed March 20, 2026, 4:54 p.m.
Created at: March 20, 2026, 1:50 p.m.