Triple
T496953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Launch System |
E10313
|
entity |
| Predicate | payloadToTLI |
P14383
|
FINISHED |
| Object | 27,000 kg (Block 1, approximate) |
—
|
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: 27,000 kg (Block 1, approximate) | Statement: [Space Launch System, payloadToTLI, 27,000 kg (Block 1, approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payloadToTLI Context triple: [Space Launch System, payloadToTLI, 27,000 kg (Block 1, approximate)]
-
A.
payloadToGTO
Indicates the maximum mass a launch system can deliver into a geostationary transfer orbit (GTO).
-
B.
payloadType
Indicates the kind or category of payload associated with or carried by an entity or action.
-
C.
payloadTo700kmSSO
Indicates the capability or action of delivering a payload into a 700-kilometer altitude sun-synchronous orbit (SSO).
-
D.
maximumPayload
Indicates the greatest amount of load or capacity that an entity is designed or allowed to carry, handle, or support.
-
E.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
- F. None of above. chosen
Provenance (4 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f116f1b4819082f88d6c747368ae |
completed | Feb. 28, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69a2edfa87cc8190a77c726a5a55b7d9 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eebbd70481908b462296671de67b |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.