Triple

T13538526
Position Surface form Disambiguated ID Type / Status
Subject Power and Propulsion Element E323321 entity
Predicate plannedLaunchConfiguration P110755 FINISHED
Object co-manifested with HALO module 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: co-manifested with HALO module | Statement: [Power and Propulsion Element, plannedLaunchConfiguration, co-manifested with HALO module]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: plannedLaunchConfiguration
Context triple: [Power and Propulsion Element, plannedLaunchConfiguration, co-manifested with HALO module]
  • A. launchProfile
    Indicates initiating or configuring the conditions, parameters, or settings under which a launch or execution process is carried out.
  • B. plannedTarget
    Indicates that one entity has been designated or selected as the intended target or objective of another entity’s planned action or operation.
  • C. originalPlannedLaunchYear
    Indicates the year that was initially scheduled or intended for an entity’s launch before any delays or changes.
  • D. plannedPayload
    Indicates that an entity is designated or scheduled to be carried, delivered, or transported as part of a planned operation or mission.
  • E. preLaunchName
    Indicates the name assigned to something before its official or public launch.
  • 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_69d8076776248190bdf0d4fa1f85a5fc completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbafd7ad9481908fe1d7ffcf8fab71 completed April 12, 2026, 2:44 p.m.
PD Predicate disambiguation batch_69dbae1046c48190b4ee98c6c9cb9d85 completed April 12, 2026, 2:37 p.m.
PDg Predicate description generation batch_69dbaecc98cc8190829f5be759c4f1e3 completed April 12, 2026, 2:40 p.m.
Created at: April 9, 2026, 9:45 p.m.