Triple

T9350316
Position Surface form Disambiguated ID Type / Status
Subject Würmsee E224998 entity
Predicate modernOfficialName P66 FINISHED
Object Starnberger See E41860 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: Starnberger See | Statement: [Würmsee, modernOfficialName, Starnberger See]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Starnberger See
Context triple: [Würmsee, modernOfficialName, Starnberger See]
  • A. Starnberger See chosen
    Starnberger See is a large, scenic lake in southern Germany known for its affluent lakeside communities, recreational activities, and historical associations with Bavarian royalty.
  • B. Jungfernsee
    Jungfernsee is a scenic lake on the outskirts of Potsdam and Berlin, known for its historic villas, palaces, and location along the former inner German border.
  • C. Ammersee
    Ammersee is a large glacial lake in southern Germany known for its scenic shores, recreational activities, and proximity to the Alps.
  • D. Scharmützelsee
    Scharmützelsee is a popular lake in eastern Germany known for its scenic surroundings, recreational activities, and spa resorts.
  • E. Grunewaldsee
    Grunewaldsee is a popular forest lake in Berlin known for its scenic surroundings and dog-friendly bathing areas.
  • 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_69ca842abfd48190949d71c3b86eeba8 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd4f9248c08190a7bb40feec2eb217 completed April 1, 2026, 5:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69d7941d893c81909f3b3bcf827e796d completed April 9, 2026, 11:57 a.m.
Created at: March 30, 2026, 7:41 p.m.