Triple
T6456380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhine–Alpine freight corridor |
E142002
|
entity |
| Predicate | cargoVolume |
P17923
|
FINISHED |
| Object | high-volume |
—
|
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: high-volume | Statement: [Rhine–Alpine freight corridor, cargoVolume, high-volume]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoVolume Context triple: [Rhine–Alpine freight corridor, cargoVolume, high-volume]
-
A.
cargoSpace
Indicates that one entity provides storage capacity or room for carrying goods, equipment, or other items for another entity.
-
B.
cargoHoldVolume
chosen
Indicates the total internal volume available within a cargo hold for storing goods or materials.
-
C.
cargoCapacityFeature
Indicates that an entity has a feature specifying how much cargo it can carry or accommodate.
-
D.
trunkVolume
Indicates the volume or capacity of an entity’s trunk or main storage compartment.
-
E.
cargoLoading
Indicates the action or process of placing cargo onto a vehicle, vessel, or other transport medium for shipment or movement.
- 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_69c008d2f91c8190a8178767a35e08fc |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069d639ec8190bb0a806da4118440 |
completed | March 22, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69c0673b44148190aed70084f0ff4992 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:48 p.m.