Triple

T13861784
Position Surface form Disambiguated ID Type / Status
Subject Loisach E333213 entity
Predicate flowsThrough P225 FINISHED
Object Wolfratshausen E509691 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: Wolfratshausen | Statement: [Loisach, flowsThrough, Wolfratshausen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wolfratshausen
Context triple: [Loisach, flowsThrough, Wolfratshausen]
  • A. Wolfratshausen chosen
    Wolfratshausen is a Bavarian town in southern Germany known for its historic old town, riverside setting on the Loisach and Isar, and proximity to Munich and the Alps.
  • B. Haßfurt
    Haßfurt is a small town in northern Bavaria, Germany, situated on the Main River and known for its historic architecture and regional administrative role.
  • C. Schwarzach
    Schwarzach is a municipality in the Austrian state of Vorarlberg, located in the district of Bregenz.
  • D. Schwarzach
    Schwarzach is a municipality in the Straubing-Bogen district of Lower Bavaria, Germany, known for its rural setting in the Bavarian Forest region.
  • E. Schwarzach
    Schwarzach is a river in Bavaria, Germany, known as a tributary of the Rednitz.
  • 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_69d81c5ced9c8190b0e9bcc6effe5959 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de05c20db88190acb842748aa01039 completed April 14, 2026, 9:15 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffa11c81f481909129eef69e47d079 completed May 9, 2026, 9:03 p.m.
Created at: April 9, 2026, 10:14 p.m.