Triple

T12094747
Position Surface form Disambiguated ID Type / Status
Subject Heiligenhaus E288041 entity
Predicate locatedNear P294 FINISHED
Object Wuppertal E173299 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: Wuppertal | Statement: [Heiligenhaus, locatedNear, Wuppertal]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wuppertal
Context triple: [Heiligenhaus, locatedNear, Wuppertal]
  • A. Wuppertal chosen
    Wuppertal is a city in western Germany known for its steep slopes, extensive parks, and the unique suspended monorail Wuppertal Schwebebahn.
  • B. Duisburg
    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.
  • C. Cologne
    Cologne is a historic German city on the Rhine River, renowned for its Gothic cathedral, vibrant cultural scene, and status as a major economic and media hub.
  • D. Krefeld
    Krefeld is a city in western Germany near the Rhine River, known historically for its textile and silk industry.
  • E. 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.
  • 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_69d6ab4964708190850585628b287b0c completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d91550ce508190babf5755e1553734 completed April 10, 2026, 3:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69f75d756bd08190a79adc9a2e6188ed completed May 3, 2026, 2:36 p.m.
Created at: April 8, 2026, 9:48 p.m.