Triple
T7722658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpaceX CRS-10 |
E175050
|
entity |
| Predicate | cargoMassToISS |
P14976
|
FINISHED |
| Object | approximately 2490 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 2490 kg | Statement: [SpaceX CRS-10, cargoMassToISS, approximately 2490 kg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoMassToISS Context triple: [SpaceX CRS-10, cargoMassToISS, approximately 2490 kg]
-
A.
cargoCapacityToISS
chosen
Indicates the amount of cargo that can be transported to the International Space Station in a given mission or by a given vehicle.
-
B.
cargoCapacityFromISS
Indicates the amount of cargo capacity that is transported from the International Space Station to another location or vehicle.
-
C.
spacecraftMass
Indicates the mass value associated with a spacecraft in a given context.
-
D.
massAtLiftoff
Indicates the total mass an object or vehicle has at the moment it leaves the ground or launch platform.
-
E.
leoPayloadCapacity
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.
- 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_69c6995d541c81909eaa646b1a8369a9 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7074eca4c8190bd51fd1b450729e8 |
completed | March 27, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69c7016a6cf88190b53bf4b958f0f302 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:05 p.m.