Triple

T14331945
Position Surface form Disambiguated ID Type / Status
Subject Duisburg port facilities E355369 entity
Predicate locatedIn P40 FINISHED
Object Duisburg E43985 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: Duisburg | Statement: [Duisburg port facilities, locatedIn, Duisburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Duisburg
Context triple: [Duisburg port facilities, locatedIn, Duisburg]
  • A. Duisburg chosen
    Duisburg is a major industrial and port city in western Germany’s Ruhr region, known for its steel production and one of the world’s largest inland harbors.
  • B. Düsseldorf
    Düsseldorf is a major German city on the Rhine River known for its fashion and art scenes, modern architecture, and status as an important economic and financial center.
  • C. Mülheim an der Ruhr
    Mülheim an der Ruhr is a city in western Germany’s Ruhr area, known for its industrial heritage, riverside setting on the Ruhr River, and role as a regional economic and cultural center.
  • D. Krefeld
    Krefeld is a city in western Germany near the Rhine River, known historically for its textile and silk industry.
  • E. Wuppertal
    Wuppertal is a city in western Germany known for its steep slopes, extensive parks, and the unique suspended monorail Wuppertal Schwebebahn.
  • 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_69d8278fa2108190bc0d0e7939c1eb03 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de8c1fb87c81908412c2953243c8e3 completed April 14, 2026, 6:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69ff4c2a938081909ccd9fe7c5021dc6 completed May 9, 2026, 3 p.m.
Created at: April 10, 2026, 1:13 a.m.