Triple

T22383631
Position Surface form Disambiguated ID Type / Status
Subject Siebengebirge E553337 entity
Predicate highestPoint P210 FINISHED
Object Ölberg NE NERFINISHED

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: Ölberg | Statement: [Siebengebirge, highestPoint, Ölberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ölberg
Context triple: [Siebengebirge, highestPoint, Ölberg]
  • A. Ölberg chosen
    Ölberg is the highest and one of the most prominent hills in Germany’s Siebengebirge range, known for its scenic views over the Rhine Valley.
  • B. Reitberg
    Reitberg is a locality or settlement that forms part of the municipality of Eugendorf in the Austrian state of Salzburg.
  • C. Eichberg
    Eichberg is a municipality in the Swiss canton of St. Gallen, situated in the Rhine Valley region near the border with Austria.
  • D. Schiedlberg
    Schiedlberg is a small municipality in the Austrian state of Upper Austria, situated in the Linz-Land District.
  • E. Todtnau
    Todtnau is a small town in Germany’s Black Forest region, known for its mountainous scenery, outdoor recreation, and proximity to the Feldberg peak.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e4cf87c8190a1ff474daec326b7 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f1582d8e548190a7330de49d519675 completed April 29, 2026, 1 a.m.
Created at: April 16, 2026, 8:45 p.m.