Triple
T38054753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starship (SpaceX) |
E949868
|
entity |
| Predicate | targetPayloadToLEO |
P42908
|
FINISHED |
| Object | >100 metric tons |
—
|
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: >100 metric tons | Statement: [Starship (SpaceX), targetPayloadToLEO, >100 metric tons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetPayloadToLEO Context triple: [Starship (SpaceX), targetPayloadToLEO, >100 metric tons]
-
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.
massToLowEarthOrbit
Indicates the amount of mass that can be transported by a launch system into low Earth orbit.
-
E.
orbitInjectionMethod
Indicates the method or technique used to insert an object into a specific orbit.
- 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_69f76f000cf081908c11fb5443b392e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff53389a0481908b2baeb43c6294f0 |
completed | May 9, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69ff52e2b4b88190b38d160d771fe14b |
completed | May 9, 2026, 3:29 p.m. |
Created at: May 3, 2026, 4:21 p.m.