Triple

T24651397
Position Surface form Disambiguated ID Type / Status
Subject Westhafen E610258 entity
Predicate isKeyLogisticsNodeFor P154729 FINISHED
Object inland freight in Berlin 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: inland freight in Berlin | Statement: [Westhafen, isKeyLogisticsNodeFor, inland freight in Berlin]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isKeyLogisticsNodeFor
Context triple: [Westhafen, isKeyLogisticsNodeFor, inland freight in Berlin]
  • A. isKeyNodeIn
    Indicates that a node serves as a primary or critical element within a specified structure, system, or context.
  • B. hasLogisticalRole
    Indicates that an entity holds a responsibility or function related to planning, coordinating, or managing logistical operations or resources.
  • C. isKeyFreightRoute
    Indicates that a transportation route serves as a primary or strategically important corridor for moving freight.
  • D. isKeyConnectionPointFor
    Indicates that something serves as a primary or critical linking point that connects or integrates other elements within a system or structure.
  • E. isKeyTransportHubIn chosen
    Indicates that a location functions as a primary node for transporting people or goods within the specified area or network.
  • 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_69e2c4d350a481909170482bc2ce6af9 completed April 17, 2026, 11:40 p.m.
NER Named-entity recognition batch_69f41011d8048190be70329ba0bfb7c7 completed May 1, 2026, 2:29 a.m.
PD Predicate disambiguation batch_69f40ed9d47881909fcfc0d04e8d074a completed May 1, 2026, 2:24 a.m.
Created at: April 18, 2026, 2:34 a.m.