Triple

T9867242
Position Surface form Disambiguated ID Type / Status
Subject Bavarian Sea E239863 entity
Predicate hasIsland P970 FINISHED
Object Frauenchiemsee E41133 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: Frauenchiemsee | Statement: [Bavarian Sea, hasIsland, Frauenchiemsee]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Frauenchiemsee
Context triple: [Bavarian Sea, hasIsland, Frauenchiemsee]
  • A. Ammersee
    Ammersee is a large glacial lake in southern Germany known for its scenic shores, recreational activities, and proximity to the Alps.
  • B. Altmühlsee
    Altmühlsee is an artificial recreational lake in Bavaria, Germany, popular for swimming, sailing, and nature conservation.
  • C. Chiemsee chosen
    Chiemsee is one of Germany’s largest lakes, famed for its scenic Alpine setting and historic islands such as Herrenchiemsee with its royal palace.
  • D. Alpsee
    Alpsee is a picturesque alpine lake in Bavaria, Germany, renowned for its clear waters and scenic setting near the royal castles of Neuschwanstein and Hohenschwangau.
  • E. 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.
  • 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_69ca84e7506c819095cbde4ff16512bb completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb3d209ac8190b9bc9ff017a132da completed April 2, 2026, 12:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69e215ac56248190a75ad5ceb8152d5a completed April 17, 2026, 11:12 a.m.
Created at: March 30, 2026, 8:36 p.m.