Triple
T23250654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unterföhring |
E581721
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object | Isar |
—
|
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 | Statement: [Unterföhring, locatedOnRiver, Isar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Isar Context triple: [Unterföhring, locatedOnRiver, Isar]
-
A.
Isar
chosen
The Isar is a major river in the Austrian and German Alps that flows through cities such as Munich before joining the Danube.
-
B.
Isar
Isar is a structured, human-readable proof language designed for writing formal proofs within the Isabelle interactive theorem prover.
-
C.
Itsar
Itsar is an alternative name for Itsari, likely referring to the same place, group, or concept under a different designation.
-
D.
Meranien
Meranien is the German name for the medieval Duchy of Merania, a former feudal territory in the Holy Roman Empire located along the Adriatic coast.
-
E.
Isar valley
The Isar valley is a scenic river valley in Bavaria, Germany, known for its picturesque landscapes, forests, and traditional towns along the Isar 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_69e24606b17c81908aba1a4911c8a8ba |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f193f5aa9081909775fb7f7dc660b3 |
completed | April 29, 2026, 5:15 a.m. |
Created at: April 17, 2026, 4:10 p.m.