Triple

T23220741
Position Surface form Disambiguated ID Type / Status
Subject Ostorfer See E580882 entity
Predicate locatedIn P40 FINISHED
Object Schwerin (urban area) 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: Schwerin (urban area) | Statement: [Ostorfer See, locatedIn, Schwerin (urban area)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schwerin (urban area)
Context triple: [Ostorfer See, locatedIn, Schwerin (urban area)]
  • A. Schwerin chosen
    Schwerin is a historic city in northern Germany known for its picturesque lakeside setting and landmark Schwerin Castle.
  • B. Neubrandenburg
    Neubrandenburg is a historic city in northeastern Germany known for its well-preserved medieval brick Gothic architecture and distinctive city wall with multiple gate towers.
  • C. Pasewalk
    Pasewalk is a small historic town in northeastern Germany, located in the state of Mecklenburg-Vorpommern near the Polish border.
  • D. Lehrte
    Lehrte is a town in Lower Saxony, Germany, located east of Hanover and known historically for its railway junction and agricultural surroundings.
  • E. Uelzen
    Uelzen is a small town in Lower Saxony, Germany, known for its distinctive Hundertwasser-designed railway station and its role as a regional transport hub.
  • 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_69e2460389408190be74f41d217799a9 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f1916870148190853874e6cf26bbc7 completed April 29, 2026, 5:04 a.m.
Created at: April 17, 2026, 4:08 p.m.