Triple
T32282425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Station 4 |
E824735
|
entity |
| Predicate | relatedMissionPhase |
—
|
GENERATED |
| Object | lunar surface operations |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedMissionPhase Context triple: [Station 4, relatedMissionPhase, lunar surface operations]
-
A.
relatedMission
Indicates that one mission is connected or associated with another mission in a meaningful way, such as by shared goals, context, participants, or timeline.
-
B.
coversMissionPhase
Indicates that one entity’s scope, responsibility, or applicability extends over a specified mission phase.
-
C.
missionProfilePhase
chosen
Indicates the specific phase or stage within a mission profile during which an action, condition, or relationship is applicable.
-
D.
currentMissionPhase
Indicates the specific phase or stage that a mission is presently in within its overall lifecycle.
-
E.
supportsMissionPhase
Indicates that one entity provides the necessary capabilities, resources, or conditions for another entity to function or be valid during a specific mission phase.
- F. None of above.
Provenance (1 batch)
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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:43 a.m.