Triple

T13121122
Position Surface form Disambiguated ID Type / Status
Subject Heckinghausen E311721 entity
Predicate hasNameInLanguage P15 FINISHED
Object Heckinghausen (German) E311721 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: Heckinghausen (German) | Statement: [Heckinghausen, hasNameInLanguage, Heckinghausen (German)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Heckinghausen (German)
Context triple: [Heckinghausen, hasNameInLanguage, Heckinghausen (German)]
  • A. Heckinghausen chosen
    Heckinghausen is a district of the German city of Wuppertal, located in the Bergisches Land region of North Rhine-Westphalia.
  • B. Alt-Lichtenberg (German)
    Alt-Lichtenberg (German) is the German name for the Alt-Lichtenberg locality, a district-level area within the Berlin borough of Lichtenberg.
  • C. Dahme (German)
    Dahme (German) is a German-language name that typically refers to a town or river in Germany, most commonly associated with locations in the state of Brandenburg.
  • D. Schier (German)
    Schier is the German name for the Chiers, a river in Western Europe that flows through Belgium, Luxembourg, and France.
  • E. Hettenshausen
    Hettenshausen is a municipality in the district of Pfaffenhofen an der Ilm in Bavaria, Germany.
  • 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_69d806a9fe888190b081e2d9ea665d6c completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98196e69081909111407ee3d9f08e completed April 10, 2026, 11:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6e286de608190bf46af2eb656bb79 completed May 3, 2026, 5:52 a.m.
Created at: April 9, 2026, 9:06 p.m.