Triple

T15392978
Position Surface form Disambiguated ID Type / Status
Subject Apollo 13 Command and Service Module Odyssey E368094 entity
Predicate damageConsequence P78832 FINISHED
Object loss of normal electrical power 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 normal electrical power | Statement: [Apollo 13 Command and Service Module Odyssey, damageConsequence, loss of normal electrical power]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: damageConsequence
Context triple: [Apollo 13 Command and Service Module Odyssey, damageConsequence, loss of normal electrical power]
  • A. damageLeadsTo chosen
    Indicates that one instance of damage causally results in or contributes to another specified outcome or condition.
  • B. damageEffect
    Indicates that one entity causes harm, reduction, or deterioration to another entity or its properties.
  • C. damageDescription
    Indicates a textual description of the nature, extent, or characteristics of damage associated with an entity or event.
  • D. damageAssociatedWith
    Indicates a relationship where one entity is linked to causing, contributing to, or being responsible for damage affecting another entity.
  • E. damageTo
    Indicates a relationship where one entity causes harm, loss, or deterioration to another entity.
  • 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_69d85a1551a08190ba2caea7cd51c639 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03e7838b48190862b43c6c8620692 completed April 16, 2026, 1:42 a.m.
PD Predicate disambiguation batch_69ded27b8cac8190bfa77698d53c5d1c completed April 14, 2026, 11:49 p.m.
Created at: April 10, 2026, 3:19 a.m.