Triple

T32746624
Position Surface form Disambiguated ID Type / Status
Subject Shuttle Carrier Aircraft E837368 entity
Predicate launchAbortSupport P179853 FINISHED
Object relocation of orbiters after transatlantic or alternate landing 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: relocation of orbiters after transatlantic or alternate landing | Statement: [Shuttle Carrier Aircraft, launchAbortSupport, relocation of orbiters after transatlantic or alternate landing]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: launchAbortSupport
Context triple: [Shuttle Carrier Aircraft, launchAbortSupport, relocation of orbiters after transatlantic or alternate landing]
  • A. launchAbortSystem
    Indicates a system designed to rapidly terminate or interrupt a launch sequence to protect the vehicle, payload, or crew in case of an emergency.
  • B. launchFailureMode
    Indicates the specific way in which a launch attempt fails or the type of failure that occurs during a launch.
  • C. abandonmentStart
    Indicates the point in time or event at which an abandonment process or state begins between the involved entities.
  • D. launchFailurePhase
    Indicates the specific phase or stage of a launch sequence during which a failure or malfunction occurs.
  • E. launchAndRecovery
    Indicates a relationship where one entity is responsible for both deploying (launching) another entity into operation and subsequently retrieving (recovering) it afterward.
  • 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_69f34936e1748190b797e406e4e9293a completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f727afd5d88190ad48735cd1b32787 completed May 3, 2026, 10:47 a.m.
PD Predicate disambiguation batch_69f72737c42c8190a3f781a5e98868ff completed May 3, 2026, 10:45 a.m.
PDg Predicate description generation batch_69f727ad9ff88190ba8069dd48b2e98f completed May 3, 2026, 10:47 a.m.
Created at: May 1, 2026, 1:12 a.m.