Triple

T13137717
Position Surface form Disambiguated ID Type / Status
Subject Blocksberg E312125 entity
Predicate hasNameInGerman P22792 FINISHED
Object Blocksberg E312125 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: Blocksberg | Statement: [Blocksberg, hasNameInGerman, Blocksberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Blocksberg
Context triple: [Blocksberg, hasNameInGerman, Blocksberg]
  • A. Blocksberg chosen
    Blocksberg is the legendary name for the Brocken, a peak in Germany’s Harz Mountains famed in folklore as a gathering place for witches, especially on Walpurgis Night.
  • B. Piekberg
    Piekberg is a low, wooded hill on the German island of Rügen, notable as its highest natural elevation.
  • C. Spiegelberg
    Spiegelberg is a rebellious and scheming member of the robber band in Friedrich Schiller’s play "Die Räuber," known for his ruthless ambition and treacherous nature.
  • D. Gamsberg
    Gamsberg is a prominent mountain in Namibia known for its flat-topped summit and exceptionally clear skies that make it a favored site for astronomical observations.
  • E. Silfverberg
    Silfverberg is a Swedish surname most notably associated with professional ice hockey player Jakob Silfverberg.
  • 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_69d981b6a4348190b9922ed255759078 completed April 10, 2026, 11:03 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6e295b3408190a7246115d3ee90e5 completed May 3, 2026, 5:52 a.m.
Created at: April 9, 2026, 9:09 p.m.