Triple

T34989370
Position Surface form Disambiguated ID Type / Status
Subject Vault Dweller E1009337 entity
Predicate canonicalOutcome P182177 FINISHED
Object exiled from Vault 13 after saving it 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: exiled from Vault 13 after saving it | Statement: [Vault Dweller, canonicalOutcome, exiled from Vault 13 after saving it]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canonicalOutcome
Context triple: [Vault Dweller, canonicalOutcome, exiled from Vault 13 after saving it]
  • A. outcomeType
    Indicates the specific category or nature of the result produced by an event, process, or action.
  • B. supportedOutcomeOf
    Indicates that one entity serves as evidence, backing, or justification for the outcome or result represented by another entity.
  • C. outcomeOf
    Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
  • D. initialOutcome
    Indicates the result or state that first occurs at the beginning of a process, event, or interaction, before any subsequent changes or outcomes.
  • E. governsOutcome
    Indicates that one entity has decisive control or influence over the result or consequence affecting 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_69f76dca50dc8190b71f39defe186be8 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78710282c81909146dc0be91e983f completed May 3, 2026, 5:34 p.m.
PD Predicate disambiguation batch_69f784162134819098413482ef52042f completed May 3, 2026, 5:21 p.m.
PDg Predicate description generation batch_69f7870dfe108190996c0c68630edc7f completed May 3, 2026, 5:34 p.m.
Created at: May 3, 2026, 4:01 p.m.