Triple
T682955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lockheed C-130 Hercules |
E13220
|
entity |
| Predicate | cargoCapacity |
P13871
|
FINISHED |
| Object | around 19,000 kg (depending on variant) |
—
|
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: around 19,000 kg (depending on variant) | Statement: [Lockheed C-130 Hercules, cargoCapacity, around 19,000 kg (depending on variant)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoCapacity Context triple: [Lockheed C-130 Hercules, cargoCapacity, around 19,000 kg (depending on variant)]
-
A.
cargoSpace
chosen
Indicates that one entity provides storage capacity or room for carrying goods, equipment, or other items for another entity.
-
B.
maximumPassengerCapacity
Indicates the greatest number of passengers that an entity is designed or allowed to carry at one time.
-
C.
cargoHoldWidth
Indicates the width dimension of a cargo hold in a vehicle, vessel, or storage structure.
-
D.
cargoCapacityFromISS
Indicates the amount of cargo capacity that is transported from the International Space Station to another location or vehicle.
-
E.
cargoBayDiameter
Indicates the diameter measurement of a cargo bay in the described context.
- 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a070d4c08190a510a8f9c1ae8076 |
completed | March 1, 2026, 8:24 p.m. |
| PD | Predicate disambiguation | batch_69a49d1f0ccc819088c1527beabcb718 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.