Triple

T3041408
Position Surface form Disambiguated ID Type / Status
Subject Oberharz am Brocken E83137 entity
Predicate hasPart P35 FINISHED
Object Königshütte E327735 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: Königshütte | Statement: [Oberharz am Brocken, hasPart, Königshütte]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Königshütte
Context triple: [Oberharz am Brocken, hasPart, Königshütte]
  • A. Königshütte chosen
    Königshütte is a village in the Harz region of central Germany, known for its scenic surroundings, reservoirs, and hiking opportunities.
  • B. Kronsberg
    Kronsberg is a location in Germany known, among other things, as the place where former Nazi youth leader Baldur von Schirach died.
  • C. Seiffen
    Seiffen is a village in Germany’s Ore Mountains renowned for its traditional wooden toy-making and iconic Christmas decorations.
  • D. Teutschenthal
    Teutschenthal is a municipality in the Saalekreis district of Saxony-Anhalt in central Germany.
  • E. Lochau
    Lochau is a locality in Germany historically noted as the place where the influential Reformation-era prince Frederick the Wise died.
  • 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_69ad8b2298908190a7cb4e9bdbf064d0 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad9b5b92088190971bed04e65c5917 completed March 8, 2026, 3:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69b20f41e2dc8190bba90185edd287ac completed March 12, 2026, 12:56 a.m.
Created at: March 8, 2026, 3:01 p.m.