Triple

T16156124
Position Surface form Disambiguated ID Type / Status
Subject A1 motorway E392046 entity
Predicate terminusNorth P3375 FINISHED
Object Heiligenhafen E802355 NE 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: Heiligenhafen | Statement: [A1 motorway, terminusNorth, Heiligenhafen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Heiligenhafen
Context triple: [A1 motorway, terminusNorth, Heiligenhafen]
  • A. Heiligenhafen chosen
    Heiligenhafen is a coastal town in northern Germany on the Baltic Sea, known for its fishing harbor, beaches, and tourism.
  • B. Ostuferhafen
    Ostuferhafen is a major ferry and cargo terminal in Kiel, Germany, serving Baltic Sea routes and handling both passenger and freight traffic.
  • C. Westhafen
    Westhafen is a major inland port and freight hub in Berlin, serving as one of the city’s key logistics and transportation centers.
  • D. Bremerhaven
    Bremerhaven is a major German port city on the North Sea, known for its maritime industry, shipbuilding, and role as a key hub for trade and logistics.
  • E. Wallhausen
    Wallhausen is a village in present-day Saxony-Anhalt, Germany, historically notable as the birthplace of Otto I, Holy Roman Emperor.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d87f1c65e48190aa2b4c472e9bafc4 completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e21e5aa57c8190a9d89dd57e30318f completed April 17, 2026, 11:49 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0007833960819088334e10258a9d72 completed May 10, 2026, 4:20 a.m.
Created at: April 10, 2026, 5:01 a.m.