Triple

T9146289
Position Surface form Disambiguated ID Type / Status
Subject Lake Starnberg E219462 entity
Predicate primaryInflow P4496 FINISHED
Object Steinbach E209637 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: Steinbach | Statement: [Lake Starnberg, primaryInflow, Steinbach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Steinbach
Context triple: [Lake Starnberg, primaryInflow, Steinbach]
  • A. Steinbach chosen
    Steinbach is a small river or stream in Bavaria, Germany, that serves as one of the tributaries feeding into Lake Starnberg (Starnberger See).
  • B. Bergneustadt
    Bergneustadt is a small town in North Rhine-Westphalia, Germany, known for its location in the hilly Oberbergischer Kreis region and its traditional half-timbered architecture.
  • C. Waldstadt
    Waldstadt is a district of Karlsruhe in the German state of Baden-Württemberg, characterized by its forested setting and primarily residential layout.
  • D. Barntrup
    Barntrup is a small town in the Lippe district of North Rhine-Westphalia, Germany, known for its historic architecture and rural surroundings.
  • E. Braunsberg
    Braunsberg is a locality in former East Prussia (now in Poland) known for its proximity to the World War II Heiligenbeil pocket battlefield.
  • 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_69ca83e121dc81909912bd66953081c5 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cca917914c8190b97ca9169bbd1e5e completed April 1, 2026, 5:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69d05458ac188190acc47fc99f8ee182 completed April 3, 2026, 11:59 p.m.
Created at: March 30, 2026, 7:20 p.m.