Triple

T14057129
Position Surface form Disambiguated ID Type / Status
Subject Peberholm E338247 entity
Predicate instanceOf P0 FINISHED
Object transport infrastructure component C2952 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: transport infrastructure component
Context triple: [Peberholm, instanceOf, transport infrastructure component]
  • A. transport infrastructure network
    A transport infrastructure network is an interconnected system of physical routes and facilities—such as roads, railways, ports, and airports—designed to enable the efficient movement of people and goods across regions.
  • B. transport infrastructure name
    A transport infrastructure name identifies a specific facility or network element used for the movement of people or goods, such as a road, railway line, airport, or port.
  • C. public transportation infrastructure
    Public transportation infrastructure encompasses the physical and organizational systems—such as buses, trains, stations, tracks, and supporting facilities—that enable the efficient movement of people via shared transit services.
  • D. rail transportation infrastructure
    Rail transportation infrastructure encompasses the physical and organizational systems—such as tracks, stations, signaling, power supply, and related facilities—required to support the safe and efficient movement of trains and rail-based services.
  • E. transport corridor chosen
    A transport corridor is a designated route or geographic band that concentrates and connects major transportation infrastructure—such as roads, railways, ports, and logistics hubs—to facilitate efficient movement of people and goods between key locations.
  • F. None of above.

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_69d81c67ba6c819091935650dfb3b895 completed April 9, 2026, 9:38 p.m.
Created at: April 9, 2026, 10:20 p.m.