Triple
T27075385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpaceX CRS-11 |
E685448
|
entity |
| Predicate | unpressurizedCargoMass |
P161822
|
FINISHED |
| Object | about 771 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: about 771 kg | Statement: [SpaceX CRS-11, unpressurizedCargoMass, about 771 kg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unpressurizedCargoMass Context triple: [SpaceX CRS-11, unpressurizedCargoMass, about 771 kg]
-
A.
unpressurizedCargoCapability
Indicates the ability of an entity to carry or transport cargo in an unpressurized space or compartment.
-
B.
usedCargoSpacecraftType
Indicates that a particular type of cargo spacecraft was employed or utilized in a given mission or context.
-
C.
isPressurizedCargoCarrier
Indicates that the entity functions as a cargo carrier whose internal space is maintained at a controlled pressure.
-
D.
pressurizedCargoModuleSupplier
Indicates a supplier relationship in which one entity provides or manufactures pressurized cargo modules for another entity.
-
E.
propellantCapacity
Indicates the amount of propellant a system, such as a rocket or spacecraft, is capable of storing or carrying.
- 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f623159a7c819089028373790db00f |
completed | May 2, 2026, 4:15 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fa35ac48190890102c348ed81a0 |
completed | May 2, 2026, 4 p.m. |
Created at: April 27, 2026, 8:31 a.m.