Triple

T10343732
Position Surface form Disambiguated ID Type / Status
Subject Franconian Jura E243688 entity
Predicate highestPoint P210 FINISHED
Object Hesselberg E445995 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: Hesselberg | Statement: [Franconian Jura, highestPoint, Hesselberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hesselberg
Context triple: [Franconian Jura, highestPoint, Hesselberg]
  • A. Hesselberg chosen
    Hesselberg is a prominent hill in Bavaria, Germany, known as the highest elevation of the Franconian Alb region.
  • B. Lutterberg
    Lutterberg is a village in Lower Saxony, Germany, historically notable as the site of the 1758 Battle of Lutterberg during the Seven Years' War.
  • C. Heilsberg
    Heilsberg is a historic town in northeastern Poland, known today as Lidzbark Warmiński, that was the site of significant medieval and Napoleonic-era military engagements.
  • D. Widdersberg
    Widdersberg is a small village that forms one of the local subdivisions of the municipality of Münsing in Bavaria, Germany.
  • E. Haldenstein
    Haldenstein is a small Swiss village in the canton of Graubünden, known in architecture circles as the longtime base of renowned architect Peter Zumthor.
  • 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_69d381b22b8c8190aaed476be5f872a9 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4e92105888190a08104deb9d0cf1c completed April 7, 2026, 11:23 a.m.
NED1 Entity disambiguation (via context triple) batch_69d75077dfbc81908de29aac1a3bb19f completed April 9, 2026, 7:08 a.m.
Created at: April 6, 2026, 11:55 a.m.