Triple
T11222067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rottal-Inn |
E265593
|
entity |
| Predicate | contains |
P35
|
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: [Rottal-Inn, contains, Simbach am Inn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Simbach am Inn Context triple: [Rottal-Inn, contains, 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.
Neuhaus am Inn
Neuhaus am Inn is a Bavarian municipality on the River Inn near the Austrian border, known for its rural character and proximity to the city of Passau.
-
C.
Neulengbach
Neulengbach is a small town in Lower Austria known for its historic center and its location within the Vienna Woods region.
-
D.
Mühldorf am Inn
Mühldorf am Inn is a historic Bavarian town in southeastern Germany situated along the River Inn.
-
E.
Neuötting
Neuötting is a small Bavarian town in southeastern Germany known for its historic town center and location near the Austrian border.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8ec8fb08190b27144ab65f85957 |
completed | April 9, 2026, 5:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5d3049e788190a7caf324a4b793d2 |
completed | April 20, 2026, 7:17 a.m. |
Created at: April 8, 2026, 9:30 p.m.