Triple
T13546667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ares V |
E323528
|
entity |
| Predicate | designPayloadToLEO |
P42908
|
FINISHED |
| Object | approximately 180000 kg |
—
|
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: approximately 180000 kg | Statement: [Ares V, designPayloadToLEO, approximately 180000 kg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designPayloadToLEO Context triple: [Ares V, designPayloadToLEO, approximately 180000 kg]
-
A.
designedPayloadToLEO
chosen
Indicates that an object (typically a launch vehicle or system) is designed to deliver a specified payload mass to Low Earth Orbit (LEO).
-
B.
designedPayloadToLunarOrbit
Indicates that something was created or engineered specifically to deliver a payload into lunar orbit.
-
C.
payloadToTransLunarInjection
Indicates that a payload is being sent onto a trajectory from Earth orbit toward the Moon (trans-lunar injection).
-
D.
designedForOrbitInsertion
Indicates that something is intended or configured to perform or facilitate the insertion of an object into orbit.
-
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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae13bec4819084c1770638c00ed9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:45 p.m.