Triple

T31793210
Position Surface form Disambiguated ID Type / Status
Subject Boeing Commercial Crew program E811523 entity
Predicate firstUncrewedOrbitalFlightResult P34098 FINISHED
Object partial failure 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: partial failure | Statement: [Boeing Commercial Crew program, firstUncrewedOrbitalFlightResult, partial failure]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: firstUncrewedOrbitalFlightResult
Context triple: [Boeing Commercial Crew program, firstUncrewedOrbitalFlightResult, partial failure]
  • A. firstOrbitalMissionOutcome chosen
    Indicates the result or status achieved by an entity’s first orbital mission.
  • B. firstSuccessfulOrbitalPayload
    Indicates that the subject entity successfully delivered its first payload into orbit.
  • C. firstUncrewedTestFlightMission
    Indicates that the subject is the first mission in which a spacecraft or launch system is tested in flight without any crew onboard.
  • D. firstOrbitalSuccessPayloadType
    Indicates the type or category of payload carried on an entity’s first successful orbital mission.
  • E. firstUncrewedTestFlight
    Indicates the event of conducting the initial test flight of a vehicle or system without any crew onboard.
  • 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_69f348e60748819082dcaa7792659803 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_6a037c894b488190bcbec2eccaff4a01 completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a0379e7aa0c8190bdc9ee4d54fc821b completed May 12, 2026, 7:05 p.m.
Created at: April 30, 2026, 11:39 p.m.