Triple

T19620500
Position Surface form Disambiguated ID Type / Status
Subject Scharnitz E470992 entity
Predicate locatedOn P40 FINISHED
Object Isar River NE NERFINISHED

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: Isar River | Statement: [Scharnitz, locatedOn, Isar River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Isar River
Context triple: [Scharnitz, locatedOn, Isar River]
  • A. Isar River chosen
    The Isar River is a major river in Austria and Germany that flows through the Alps and the city of Munich before joining the Danube.
  • B. Inn River
    The Inn River is a major Alpine river in Central Europe that flows through Switzerland, Austria, and Germany before joining the Danube.
  • C. Würm River
    The Würm River is a small river in Bavaria, Germany, known for flowing north from Lake Starnberg through towns such as Gauting and Starnberg before joining the Amper River.
  • D. Schwechat River
    The Schwechat River is a waterway in eastern Austria that flows through Lower Austria and the town of Schwechat before joining the Danube.
  • E. Hase River
    The Hase River is a river in northwestern Germany that flows through Lower Saxony and North Rhine-Westphalia before joining the Ems River.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e510fa248190b7afb274a1d4cf73 completed April 10, 2026, 11:54 a.m.
NER Named-entity recognition batch_69e640e512d08190a76bf81b3282e0e5 completed April 20, 2026, 3:06 p.m.
Created at: April 10, 2026, 1:43 p.m.