Triple

T1839126
Position Surface form Disambiguated ID Type / Status
Subject Inn E41132 entity
Predicate flowsThrough P225 FINISHED
Object Simbach am Inn E59075 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: Simbach am Inn | Statement: [Inn, flowsThrough, Simbach am Inn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Simbach am Inn
Context triple: [Inn, flowsThrough, Simbach am Inn]
  • A. Simbach am Inn chosen
    Simbach am Inn is a Bavarian town in southeastern Germany situated on the River Inn directly across from the Austrian town of Braunau am Inn.
  • B. Mühldorf am Inn
    Mühldorf am Inn is a historic Bavarian town in southeastern Germany situated along the River Inn.
  • C. Steinheim am Albuch
    Steinheim am Albuch is a small municipality in the Swabian Alb region of Baden-Württemberg, Germany, known for the nearby Steinheim meteorite crater.
  • D. Heidenheim an der Brenz
    Heidenheim an der Brenz is a town in the German state of Baden-Württemberg known for its industrial heritage, historic castle Hellenstein, and location on the Brenz River near the Swabian Jura.
  • E. Essling
    Essling is a village near Vienna, Austria, historically notable as one of the sites of the 1809 Battle of Aspern-Essling during the Napoleonic Wars.
  • 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_69a88647f9388190909bc36e795bdaec completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb03b3eb08190ae68d8476fc89c7f completed March 7, 2026, 4:57 a.m.
NED1 Entity disambiguation (via context triple) batch_69adfba141fc819084cf5903eced2326 completed March 8, 2026, 10:43 p.m.
Created at: March 4, 2026, 7:33 p.m.