Triple

T20314741
Position Surface form Disambiguated ID Type / Status
Subject Hamburg–Copenhagen E510349 entity
Predicate historicalRouteVia P139623 FINISHED
Object Lübeck NE NERFINISHED

How this triple was built (3 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: Lübeck | Statement: [Hamburg–Copenhagen, historicalRouteVia, Lübeck]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lübeck
Context triple: [Hamburg–Copenhagen, historicalRouteVia, Lübeck]
  • A. Lübeck chosen
    Lübeck is a historic Hanseatic city in northern Germany renowned for its medieval architecture and long-standing role as a key trading hub on the Baltic Sea.
  • B. Itzehoe
    Itzehoe is a historic town in northern Germany known for its medieval origins and role as a regional center in the state of Schleswig-Holstein.
  • C. Rostock
    Rostock is a historic Hanseatic city in northern Germany known for its significant seaport on the Baltic Sea and its long maritime and trading tradition.
  • D. Flensburg
    Flensburg is a historic port city in northern Germany near the Danish border, known for its maritime heritage and role as a regional administrative and cultural center in Schleswig-Holstein.
  • E. Wismar
    Wismar is a historic Hanseatic port city on Germany’s Baltic Sea coast, known for its well-preserved medieval architecture and UNESCO-listed old town.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalRouteVia
Context triple: [Hamburg–Copenhagen, historicalRouteVia, Lübeck]
  • A. historicalRouteName
    Indicates that an entity has or is associated with a name it held historically as a route or pathway, distinct from its current official name.
  • B. historicRoute
    Indicates that a route has historical significance, typically due to its age, past usage, or role in notable events.
  • C. nearHistoricalRoute
    Indicates that one entity is located close to a historically significant route or pathway.
  • D. mappingHistory
    Indicates the historical record of how one set of elements has been mapped or associated to another over time.
  • E. hasHistoricalRoute
    Indicates that an entity possesses or is associated with a route that has historical significance or origin.
  • F. None of above. chosen

Provenance (4 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_69e0b4c7491c8190961113c4283b10b0 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e67786f4dc8190b02a6c2a4338362d completed April 20, 2026, 6:59 p.m.
PD Predicate disambiguation batch_69e55b21b09081909e46691b6f45a07f completed April 19, 2026, 10:45 p.m.
PDg Predicate description generation batch_69e56702ad04819099c1c08f28d16809 completed April 19, 2026, 11:36 p.m.
Created at: April 16, 2026, 11:19 a.m.