Triple
T2736314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starship Human Landing System |
E60638
|
entity |
| Predicate | designedForMissionType |
P17730
|
FINISHED |
| Object | crewed lunar 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: crewed lunar landing | Statement: [Starship Human Landing System, designedForMissionType, crewed lunar landing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForMissionType Context triple: [Starship Human Landing System, designedForMissionType, crewed lunar landing]
-
A.
typeOfMission
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
-
B.
supportsMissionType
chosen
Indicates that one entity is capable of handling, enabling, or being compatible with a specified type of mission.
-
C.
missionCharacteristic
Indicates that a mission possesses a specific attribute, feature, or quality that characterizes its nature or execution.
-
D.
primaryMissionTo
Indicates that an entity has a main or principal mission directed toward or focused on another entity.
-
E.
missionDurationCapability
Indicates the length of time an entity is capable of sustaining or performing a mission or operation.
- 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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb11c66c81909058f2978aa5fae9 |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.