Triple
T2833975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Block 1B |
E62305
|
entity |
| Predicate | designedPayloadToTransLunarInjection |
P4020
|
FINISHED |
| Object | greater than SLS Block 1 |
—
|
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: greater than SLS Block 1 | Statement: [Block 1B, designedPayloadToTransLunarInjection, greater than SLS Block 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedPayloadToTransLunarInjection Context triple: [Block 1B, designedPayloadToTransLunarInjection, greater than SLS Block 1]
-
A.
ArtemisIITrajectory
Indicates the flight path or orbital route followed by the Artemis II mission spacecraft during its journey.
-
B.
spacecraftDestination
Indicates that a spacecraft is intended to travel to, arrive at, or be directed toward a particular destination.
-
C.
plannedPayload
Indicates that an entity is designated or scheduled to be carried, delivered, or transported as part of a planned operation or mission.
-
D.
launchVehicle
chosen
Indicates that one entity serves as the rocket or carrier used to launch another entity (such as a payload, spacecraft, or mission) into space or a target trajectory.
-
E.
missionPatchDesigner
Indicates that one entity is the designer or creator of the mission patch associated with another entity (typically a space mission).
- 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdec18b808190aedae2ed11d53b15 |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd0ce8b08190ba28c192988f38ce |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.