Triple
T36660082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 14 Command and Service Module |
E905094
|
entity |
| Predicate | supportedMissionPhase |
P37048
|
FINISHED |
| Object | launch |
—
|
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: launch | Statement: [Apollo 14 Command and Service Module, supportedMissionPhase, launch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedMissionPhase Context triple: [Apollo 14 Command and Service Module, supportedMissionPhase, launch]
-
A.
supportsMissionPhase
chosen
Indicates that one entity provides the necessary capabilities, resources, or conditions for another entity to function or be valid during a specific mission phase.
-
B.
supportsMissionType
Indicates that one entity is capable of handling, enabling, or being compatible with a specified type of mission.
-
C.
coversMissionPhase
Indicates that one entity’s scope, responsibility, or applicability extends over a specified mission phase.
-
D.
supportsMissionArea
Indicates that one entity contributes to, enables, or aligns with the objectives and activities of a specified mission area.
-
E.
supportsMissionData
Indicates that one entity provides the necessary functionality or resources for another entity’s mission-related data to be stored, processed, or utilized.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.