Triple
T11187910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Glenn |
E264720
|
entity |
| Predicate | launchToLEO |
P84008
|
FINISHED |
| Object | heavy-lift class capability |
—
|
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: heavy-lift class capability | Statement: [New Glenn, launchToLEO, heavy-lift class capability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchToLEO Context triple: [New Glenn, launchToLEO, heavy-lift class capability]
-
A.
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.
-
B.
massToLowEarthOrbit
chosen
Indicates the amount of mass that can be transported by a launch system into low Earth orbit.
-
C.
primaryLaunchVehicleForCargo
Indicates that a launch vehicle is the main rocket used to carry a specific cargo into space.
-
D.
payloadToTransLunarInjection
Indicates that a payload is being sent onto a trajectory from Earth orbit toward the Moon (trans-lunar injection).
-
E.
launchVehicleRole
Indicates the functional role or purpose that an entity serves in relation to a launch vehicle within a launch or mission context.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8ad143481908d5dacc95837ecfd |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf4461c8190af84060f7db83211 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.