Triple
T11791800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-108 |
E280404
|
entity |
| Predicate | payloadMass |
P38968
|
FINISHED |
| Object | ~4,800 kg to ISS |
—
|
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: ~4,800 kg to ISS | Statement: [STS-108, payloadMass, ~4,800 kg to ISS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payloadMass Context triple: [STS-108, payloadMass, ~4,800 kg to ISS]
-
A.
returnCargoMass
Indicates the mass of cargo that is brought back or returned from a mission, trip, or transport operation.
-
B.
spacecraftMass
Indicates the mass value associated with a spacecraft in a given context.
-
C.
massAtLiftoff
Indicates the total mass an object or vehicle has at the moment it leaves the ground or launch platform.
-
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.
maximumPayload
Indicates the greatest amount of load or capacity that an entity is designed or allowed to carry, handle, or support.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a588d2c881909783c2d678c2a474 |
completed | April 10, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69d8a2491f048190853239bc05090bf4 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.