Triple

T7407354
Position Surface form Disambiguated ID Type / Status
Subject Neubrandenburg E170908 entity
Predicate locatedOn P40 FINISHED
Object Tollensesee E343097 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: Tollensesee | Statement: [Neubrandenburg, locatedOn, Tollensesee]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tollensesee
Context triple: [Neubrandenburg, locatedOn, Tollensesee]
  • A. Tollensesee chosen
    Tollensesee is a large glacial lake in northeastern Germany, known for its scenic surroundings and recreational opportunities near the city of Neubrandenburg.
  • B. Stölpchensee
    Stölpchensee is a small lake in southwestern Berlin, Germany, known for its scenic setting within the Grunewald forest and its connection to the nearby Großer Wannsee.
  • C. Ziegelsee
    Ziegelsee is a lake in the city of Schwerin in northern Germany, known for its scenic waterfront and role in the region’s interconnected lake system.
  • D. Würmsee
    Würmsee is the historical name of the Bavarian lake now known as Starnberger See, one of Germany’s largest and most famous lakes near Munich.
  • E. Küssnachtersee
    Küssnachtersee is a narrow northern arm of Lake Lucerne in central Switzerland, bordered by picturesque lakeside villages and surrounded by gentle pre-Alpine hills.
  • 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_69c68a6010108190925e5284de022660 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f298f2388190afc944c9bc78749a completed March 27, 2026, 9:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69c81ed79680819087a56082e968c266 completed March 28, 2026, 6:32 p.m.
Created at: March 27, 2026, 3:10 p.m.