Triple
T14578506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antonov An-26 |
E342121
|
entity |
| Predicate | cargoLoadingFeature |
P82844
|
FINISHED |
| Object | rear loading ramp |
—
|
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: rear loading ramp | Statement: [Antonov An-26, cargoLoadingFeature, rear loading ramp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoLoadingFeature Context triple: [Antonov An-26, cargoLoadingFeature, rear loading ramp]
-
A.
cargoLoading
Indicates the action or process of placing cargo onto a vehicle, vessel, or other transport medium for shipment or movement.
-
B.
cargoCapacityFeature
Indicates that an entity has a feature specifying how much cargo it can carry or accommodate.
-
C.
vehicleLoadingMethod
chosen
Indicates the method or process by which a vehicle is loaded with goods, passengers, or other cargo.
-
D.
cargoCapacityConfigurable
Indicates that the cargo capacity of an entity can be adjusted or configured rather than being fixed.
-
E.
cargoSystem
Indicates a relationship where an entity is part of, managed by, or associated with a cargo-handling or cargo-management system.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb3f6f78c81908a30ecb4c025299d |
completed | April 14, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:24 a.m.