Triple
T13767148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilyushin Il-76 |
E330777
|
entity |
| Predicate | typicalCargoCapacity |
P1931
|
FINISHED |
| Object | 40000 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: 40000 kg | Statement: [Ilyushin Il-76, typicalCargoCapacity, 40000 kg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCargoCapacity Context triple: [Ilyushin Il-76, typicalCargoCapacity, 40000 kg]
-
A.
designedCargoCapacity
Indicates the maximum amount of cargo an object (such as a vehicle or container) was originally engineered or specified to carry.
-
B.
typicalReturnCargo
Indicates that something is the kind of cargo that is usually carried back on a return trip or journey.
-
C.
cargoCapacityFeature
Indicates that an entity has a feature specifying how much cargo it can carry or accommodate.
-
D.
cargoCapacityConfigurable
Indicates that the cargo capacity of an entity can be adjusted or configured rather than being fixed.
-
E.
typicalCapacity
chosen
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0227f2c48190983ccc9395e4e7a2 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:10 p.m.