Triple

T13208478
Position Surface form Disambiguated ID Type / Status
Subject Harz National Park E314425 entity
Predicate highestPoint P210 FINISHED
Object Brocken E79319 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: Brocken | Statement: [Harz National Park, highestPoint, Brocken]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Brocken
Context triple: [Harz National Park, highestPoint, Brocken]
  • A. Brocken chosen
    Brocken is a prominent mountain in central Germany’s Harz range, known for its harsh climate, folklore, and role in literature and cultural history.
  • B. Bärenkopf
    Bärenkopf is a mountain peak in the Austrian Alps that forms part of the Glockner Group.
  • C. Teufelstättkopf
    Teufelstättkopf is a mountain peak in the Bavarian Ammergau Alps, popular with hikers for its scenic views and relatively accessible trails.
  • D. Kofel
    Kofel is a distinctive, steep limestone peak overlooking the town of Oberammergau in the Ammergau Alps of Bavaria, Germany, popular with hikers and climbers.
  • E. Berghaupten
    Berghaupten is a small municipality in the Ortenau district of Baden-Württemberg in southwestern Germany, known for its scenic location in the Black Forest 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_69d806aee7308190b70a237ba2a6e3e1 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98c9cb7ac819095cff8699993c419 completed April 10, 2026, 11:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69f72662a7088190b0aacc47b37390f4 completed May 3, 2026, 10:41 a.m.
Created at: April 9, 2026, 9:17 p.m.