Triple

T16997937
Position Surface form Disambiguated ID Type / Status
Subject Tegel waterfront E412364 entity
Predicate locatedOnBodyOfWater P212 FINISHED
Object Lake Tegel 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: Lake Tegel | Statement: [Tegel waterfront, locatedOnBodyOfWater, Lake Tegel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lake Tegel
Context triple: [Tegel waterfront, locatedOnBodyOfWater, Lake Tegel]
  • A. Lake Tegel chosen
    Lake Tegel is a large lake in the northwest of Berlin, Germany, known for its recreational areas, beaches, and surrounding forests.
  • B. Fennpfuhl lake
    Fennpfuhl lake is an urban pond in the Berlin district of Lichtenberg, known for its surrounding park and residential high-rises.
  • C. Muldestausee
    Muldestausee is a municipality in the district of Anhalt-Bitterfeld in Saxony-Anhalt, Germany, known for the large Mulde reservoir and its surrounding natural and recreational areas.
  • D. Stadtsee
    Stadtsee is a small lake located in the town of Bad Waldsee in southern Germany, known for its scenic setting and recreational use.
  • E. Lake Heiligensee
    Lake Heiligensee is a small freshwater lake in the Heiligensee district of Berlin, Germany, known for its recreational use and scenic natural surroundings.
  • 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_69d886cb581c8190ab05f4b429c9cd85 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d37c16d081908ea5e25c992cb254 completed April 18, 2026, 6:54 p.m.
Created at: April 10, 2026, 5:32 a.m.