Triple
T37030946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LauncherOne |
E916490
|
entity |
| Predicate | payloadCapacityToSSO |
P177770
|
FINISHED |
| Object | approximately 300 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 300 kg | Statement: [LauncherOne, payloadCapacityToSSO, approximately 300 kg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payloadCapacityToSSO Context triple: [LauncherOne, payloadCapacityToSSO, approximately 300 kg]
-
A.
payloadTo500kmSSO
chosen
Indicates the maximum payload mass a launch system can deliver into a 500-kilometer sun-synchronous orbit.
-
B.
payloadTo700kmSSO
Indicates the capability or action of delivering a payload into a 700-kilometer altitude sun-synchronous orbit (SSO).
-
C.
externalPayloadCapacity
Indicates the maximum weight of payload that can be carried externally (outside the main body or cargo area) by an entity.
-
D.
maximumPayload
Indicates the greatest amount of load or capacity that an entity is designed or allowed to carry, handle, or support.
-
E.
payloadCapability
Indicates the capacity or suitability of an entity to carry, support, or transport a specified payload.
- 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_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.