Triple
T6348452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mi-17 |
E142804
|
entity |
| Predicate | cargoCapacityExternalSling |
P18218
|
FINISHED |
| Object | approximately 4000 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 4000 kg | Statement: [Mi-17, cargoCapacityExternalSling, approximately 4000 kg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoCapacityExternalSling Context triple: [Mi-17, cargoCapacityExternalSling, approximately 4000 kg]
-
A.
cargoCapacityFeature
Indicates that an entity has a feature specifying how much cargo it can carry or accommodate.
-
B.
designedCargoCapacity
chosen
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.
cargoHoldWidth
Indicates the width dimension of a cargo hold in a vehicle, vessel, or storage structure.
-
E.
towingCapability
Indicates the maximum load or object weight that one entity is able to pull or tow.
- 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_69c008d6dcbc8190aa1c2f1fd8916b42 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067bba1988190b51f0a22e4279e1b |
completed | March 22, 2026, 10:05 p.m. |
| PD | Predicate disambiguation | batch_69c060ea1a988190889e47b7e0c819b8 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:31 p.m.