Triple
T2546126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragon 1 |
E57905
|
entity |
| Predicate | unpressurizedCargoCarrier |
P13871
|
FINISHED |
| Object | trunk |
—
|
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: trunk | Statement: [Dragon 1, unpressurizedCargoCarrier, trunk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unpressurizedCargoCarrier Context triple: [Dragon 1, unpressurizedCargoCarrier, trunk]
-
A.
cargoSpace
chosen
Indicates that one entity provides storage capacity or room for carrying goods, equipment, or other items for another entity.
-
B.
designedCargoCapacity
Indicates the maximum amount of cargo an object (such as a vehicle or container) was originally engineered or specified to carry.
-
C.
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.
-
D.
carriedBy
Indicates that one entity is physically supported and transported by another entity.
-
E.
cargoBayLength
Indicates the length measurement of a cargo bay in a vehicle, vessel, or structure.
- 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2e5152c8190b31a5e732d0dde44 |
completed | March 7, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.