Triple

T8950752
Position Surface form Disambiguated ID Type / Status
Subject Sankt Vith canton E213339 entity
Predicate contains P35 FINISHED
Object Burg-Reuland E238426 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: Burg-Reuland | Statement: [Sankt Vith canton, contains, Burg-Reuland]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Burg-Reuland
Context triple: [Sankt Vith canton, contains, Burg-Reuland]
  • A. Burg-Reuland chosen
    Burg-Reuland is a municipality in the Belgian province of Liège, known for its historic castle ruins and location in the German-speaking region of eastern Belgium.
  • B. Ritterhude
    Ritterhude is a small town in northern Germany’s Lower Saxony, situated just northwest of Bremen.
  • C. Rummelsburg
    Rummelsburg is a locality in the Berlin borough of Lichtenberg, known for its lakeside setting along the Rummelsburger See and a mix of industrial heritage and newer residential developments.
  • D. Ronsdorf
    Ronsdorf is a district of the German city of Wuppertal in North Rhine-Westphalia, historically known as an independent town in the Bergisches Land region.
  • E. Wilhelmsruh
    Wilhelmsruh is a locality in the borough of Pankow in Berlin, Germany, known for its residential character and historical ties to Berlin’s former border zone.
  • 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_69ca839843408190a39069a029a89f15 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc670c7244819084978922a9835bc9 completed April 1, 2026, 12:30 a.m.
NED1 Entity disambiguation (via context triple) batch_69d190b5bb70819082b8eeb18bd5f1f6 completed April 4, 2026, 10:29 p.m.
Created at: March 30, 2026, 6:59 p.m.