Triple

T5706146
Position Surface form Disambiguated ID Type / Status
Subject Lost in Space (1998 film) E125787 entity
Predicate disasterElement P15089 FINISHED
Object sabotage of the Jupiter 2 mission 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: sabotage of the Jupiter 2 mission | Statement: [Lost in Space (1998 film), disasterElement, sabotage of the Jupiter 2 mission]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: disasterElement
Context triple: [Lost in Space (1998 film), disasterElement, sabotage of the Jupiter 2 mission]
  • A. notableDisasterType
    Indicates the specific kind or category of disaster for which something (such as a place, event, or entity) is notable or best known.
  • B. hasDisaster chosen
    Indicates that an entity experiences, is affected by, or is associated with a disaster event.
  • C. supportsDisasterType
    Indicates that one entity is capable of handling, responding to, or being applicable to a specified type of disaster.
  • D. infrastructureDamage
    Indicates damage or destruction affecting physical infrastructure such as buildings, roads, utilities, or other constructed facilities.
  • E. frequentNaturalHazard
    Indicates that a location or area regularly experiences natural hazards such as floods, earthquakes, storms, or similar events with notable frequency.
  • 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_69c0082d6fe48190b777fb383769e5c8 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0248751bc8190b12aaa42d1ef17e3 completed March 22, 2026, 5:19 p.m.
PD Predicate disambiguation batch_69c021c2d8bc8190b947c7d1f423d2f3 completed March 22, 2026, 5:07 p.m.
Created at: March 22, 2026, 3:45 p.m.