Triple
T37720657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpX-1 |
E939572
|
entity |
| Predicate | cargoMassReturnApproximate |
P78788
|
FINISHED |
| Object | About 759 kg of cargo returned from 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: About 759 kg of cargo returned from ISS | Statement: [SpX-1, cargoMassReturnApproximate, About 759 kg of cargo returned from ISS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoMassReturnApproximate Context triple: [SpX-1, cargoMassReturnApproximate, About 759 kg of cargo returned from ISS]
-
A.
returnCargoMass
chosen
Indicates the mass of cargo that is brought back or returned from a mission, trip, or transport operation.
-
B.
billedWeight
Indicates the weight value used for billing or charging purposes in a transaction or shipment.
-
C.
cargoMassDelivered
Indicates that a certain mass of cargo has been successfully transported and delivered from a source to a destination.
-
D.
cargoQuantity
Indicates the amount or volume of cargo associated with a shipment, transport, or storage event.
-
E.
approximateMass
Indicates that one entity has a mass value that is an estimate or close approximation of the mass of another entity.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:18 p.m.