Triple

T14125736
Position Surface form Disambiguated ID Type / Status
Subject Wupper basin E340025 entity
Predicate containsTown P847 FINISHED
Object Heiligenhaus E288041 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: Heiligenhaus | Statement: [Wupper basin, containsTown, Heiligenhaus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Heiligenhaus
Context triple: [Wupper basin, containsTown, Heiligenhaus]
  • A. Heiligenhaus chosen
    Heiligenhaus is a small town in North Rhine-Westphalia, western Germany, known for its manufacturing industry and location between Düsseldorf and Essen.
  • B. Culemborg
    Culemborg is a historic town in the Dutch province of Gelderland, known for its medieval center and role in the early Dutch colonial era.
  • C. Rolandswerth
    Rolandswerth is a district of the German town of Remagen, situated along the Rhine River in the state of Rhineland-Palatinate.
  • D. Aldenhoven
    Aldenhoven is a small municipality in western Germany’s North Rhine-Westphalia, situated near the city of Aachen.
  • E. Sassenheim
    Sassenheim is a town in the Dutch province of South Holland, known historically for its bulb-growing industry and location within the Duin- en Bollenstreek (Dune and Bulb Region).
  • 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_69d81c6a95b481909e39111e0c1f31ee completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de6096976481909dc79066c5165a50 completed April 14, 2026, 3:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd5bb3da748190a29652e17dbeac33 completed May 8, 2026, 3:42 a.m.
Created at: April 9, 2026, 10:22 p.m.