Triple

T10968536
Position Surface form Disambiguated ID Type / Status
Subject Waldeck-Frankenberg E259169 entity
Predicate hasMountainRange P651 FINISHED
Object Kellerwald E99826 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: Kellerwald | Statement: [Waldeck-Frankenberg, hasMountainRange, Kellerwald]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kellerwald
Context triple: [Waldeck-Frankenberg, hasMountainRange, Kellerwald]
  • A. Kellerwald chosen
    Kellerwald is a low mountain forest region in central Germany known for its ancient beech woodlands and protected national park status.
  • B. Rheinwald
    Rheinwald is a remote alpine valley region in southeastern Switzerland known for its dramatic mountain scenery and traditional villages.
  • C. Schwanfeld
    Schwanfeld is a small municipality in the Lower Franconia region of Bavaria, Germany, known for its rural character and historical roots.
  • D. Radeberg
    Radeberg is a small town in the German state of Saxony, known for its Radeberger Pilsner brewery and historic town center near Dresden.
  • E. Rübeland
    Rübeland is a village in the Harz Mountains of central Germany, known for its show caves and scenic natural surroundings.
  • 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_69d6aa895f4c8190887a15460ef622f4 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d7719800388190943a0bffa48a2731 completed April 9, 2026, 9:30 a.m.
NED1 Entity disambiguation (via context triple) batch_69e3743d16ac81909c2d4eb11713512b completed April 18, 2026, 12:08 p.m.
Created at: April 8, 2026, 9:24 p.m.