Triple
T12211513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nizhny Novgorod river port |
E290971
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cargo-passenger terminal |
C31104
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: cargo-passenger terminal Context triple: [Nizhny Novgorod river port, instanceOf, cargo-passenger terminal]
-
A.
passenger rail terminal
A passenger rail terminal is a dedicated facility where travelers board, disembark, and transfer between trains, supported by platforms, ticketing, waiting areas, and related passenger services.
-
B.
cargo airport
A cargo airport is a specialized aviation facility designed primarily for the handling, storage, and transportation of freight and mail, featuring extensive logistics infrastructure and limited or no passenger services.
-
C.
passenger terminal area
A passenger terminal area is a designated zone within a transportation facility where travelers access services such as check-in, security, boarding, and baggage claim.
-
D.
passenger terminal concourse
A passenger terminal concourse is a large, central circulation space within a transport terminal where travelers move between entrances, ticketing, security, and boarding areas, often containing seating, retail, and information services.
-
E.
container terminal complex
A container terminal complex is a large, integrated facility where containerized cargo is transferred between ships, trucks, and trains, supported by specialized infrastructure, equipment, and logistics services.
- F. None of above. chosen
Provenance (1 batch)
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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:51 p.m.