Triple
T16741334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CH-47F Chinook |
E406840
|
entity |
| Predicate | internalCargoCapacity |
P46451
|
FINISHED |
| Object | approximately 10,886 kilograms |
—
|
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 10,886 kilograms | Statement: [CH-47F Chinook, internalCargoCapacity, approximately 10,886 kilograms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internalCargoCapacity Context triple: [CH-47F Chinook, internalCargoCapacity, approximately 10,886 kilograms]
-
A.
designedCargoCapacity
Indicates the maximum amount of cargo an object (such as a vehicle or container) was originally engineered or specified to carry.
-
B.
cargoCapacityFeature
chosen
Indicates that an entity has a feature specifying how much cargo it can carry or accommodate.
-
C.
cargoCapacityConfigurable
Indicates that the cargo capacity of an entity can be adjusted or configured rather than being fixed.
-
D.
cargoSpace
Indicates that one entity provides storage capacity or room for carrying goods, equipment, or other items for another entity.
-
E.
cargoHoldVolume
Indicates the total internal volume available within a cargo hold for storing goods or materials.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c3e87348190acaf7c40e8f8b566 |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.