Triple

T9151499
Position Surface form Disambiguated ID Type / Status
Subject District of Starnberg E219595 entity
Predicate contains P35 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: [District of Starnberg, contains, Starnberger See]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Starnberger See
Context triple: [District of Starnberg, contains, 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_69ca83e25418819093c6503deeaf30de completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cca96cf4548190a3a45172f0e9d0ec completed April 1, 2026, 5:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69d5a92795cc819087578d02c2c791e4 completed April 8, 2026, 1:02 a.m.
Created at: March 30, 2026, 7:20 p.m.