Triple
T13546671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ares V |
E323528
|
entity |
| Predicate | massAtLiftoffPlanned |
P25126
|
FINISHED |
| Object | about 3900000 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: about 3900000 kg | Statement: [Ares V, massAtLiftoffPlanned, about 3900000 kg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: massAtLiftoffPlanned Context triple: [Ares V, massAtLiftoffPlanned, about 3900000 kg]
-
A.
massAtLiftoff
chosen
Indicates the total mass an object or vehicle has at the moment it leaves the ground or launch platform.
-
B.
massToLowEarthOrbit
Indicates the amount of mass that can be transported by a launch system into low Earth orbit.
-
C.
hasLiftOrLaunchSystem
Indicates that an entity is equipped with, or associated with, a system used to lift, launch, or otherwise deploy another object or vehicle.
-
D.
launchVehicle
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.
landingModuleMass
Indicates the mass of a landing module involved in a landing operation or configuration.
- 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.