Triple
T16095900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isarbrücke Bad Tölz |
E390483
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Isar River |
E118598
|
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: Isar River | Statement: [Isarbrücke Bad Tölz, namedAfter, Isar River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Isar River Context triple: [Isarbrücke Bad Tölz, namedAfter, 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 (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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1859283008190baac96142b5c7e53 |
completed | April 17, 2026, 12:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a018c32b4a88190a07db59965b38890 |
completed | May 11, 2026, 7:58 a.m. |
Created at: April 10, 2026, 4:59 a.m.