Triple
T37030945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LauncherOne |
E916490
|
entity |
| Predicate | payloadCapacityToLEO |
P38968
|
FINISHED |
| Object | approximately 500 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 500 kg | Statement: [LauncherOne, payloadCapacityToLEO, approximately 500 kg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payloadCapacityToLEO Context triple: [LauncherOne, payloadCapacityToLEO, approximately 500 kg]
-
A.
designedPayloadToLEO
Indicates that an object (typically a launch vehicle or system) is designed to deliver a specified payload mass to Low Earth Orbit (LEO).
-
B.
massToLowEarthOrbit
Indicates the amount of mass that can be transported by a launch system into low Earth orbit.
-
C.
cargoCapacityToISS
Indicates the amount of cargo that can be transported to the International Space Station in a given mission or by a given vehicle.
-
D.
leoPayloadCapacity
chosen
Indicates the maximum payload mass or capacity that can be delivered to Low Earth Orbit (LEO) in the context of a launch vehicle or space mission.
-
E.
cargoCapacityFromISS
Indicates the amount of cargo capacity that is transported from the International Space Station to another location or vehicle.
- 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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.