Triple

T14926935
Position Surface form Disambiguated ID Type / Status
Subject Sächsische Schweiz-Osterzgebirge E372156 entity
Predicate containsTown P847 FINISHED
Object Stolpen E987150 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: Stolpen | Statement: [Sächsische Schweiz-Osterzgebirge, containsTown, Stolpen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stolpen
Context triple: [Sächsische Schweiz-Osterzgebirge, containsTown, Stolpen]
  • A. Stolpen chosen
    Stolpen is a small historic town in Saxony, Germany, best known for its medieval castle and its association with Countess Cosel.
  • B. Riesa
    Riesa is a town in the German state of Saxony, situated on the Elbe River and known historically as an important regional railway and industrial center.
  • C. Prenzlau
    Prenzlau is a historic town in northeastern Germany’s Brandenburg region, known for its medieval architecture and role as a regional administrative center.
  • D. Boltenhagen
    Boltenhagen is a Baltic Sea seaside resort town in northern Germany known for its beaches and tourism.
  • E. Treuenbrietzen
    Treuenbrietzen is a historic town in the German state of Brandenburg, known for its medieval architecture and role in Reformation-era history.
  • 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_69d85cc9da0c81908d583ca3f63a3908 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded633da0c8190b39f606212e48e71 completed April 15, 2026, 12:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe72c4f9c481909642efccb29f71d4 completed May 8, 2026, 11:33 p.m.
Created at: April 10, 2026, 2:35 a.m.