Triple

T136105
Position Surface form Disambiguated ID Type / Status
Subject Saturn E2749 entity
Predicate closureContext P5258 FINISHED
Object post-2009 GM bankruptcy restructuring 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: post-2009 GM bankruptcy restructuring | Statement: [Saturn, closureContext, post-2009 GM bankruptcy restructuring]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: closureContext
Context triple: [Saturn, closureContext, post-2009 GM bankruptcy restructuring]
  • A. releaseContext
    Indicates ending or relinquishing a previously established context or state associated with an interaction or process.
  • B. context
    Indicates that one entity provides the surrounding circumstances, setting, or background within which another entity, event, or statement occurs or is interpreted.
  • C. contextOf
    Indicates that one entity provides the situational, informational, or environmental background within which another entity exists, occurs, or is interpreted.
  • D. conflictContext
    Indicates the situational background or circumstances within which a conflict between entities occurs or is interpreted.
  • E. bindingOn
    Indicates that one party is legally or formally obligated to follow, accept, or be governed by a decision, rule, or agreement established by another.
  • 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_69a2520c0f3481908b0ed054a2fca8d0 completed Feb. 28, 2026, 2:25 a.m.
NER Named-entity recognition batch_69a257a4edf081908c494c8370c76b9a completed Feb. 28, 2026, 2:49 a.m.
PD Predicate disambiguation batch_69a25651b9048190a6277b7fec98c1ea completed Feb. 28, 2026, 2:43 a.m.
PDg Predicate description generation batch_69a256c72f6c81909b619b90d829d86e completed Feb. 28, 2026, 2:45 a.m.
Created at: Feb. 28, 2026, 2:30 a.m.