Triple
T9413977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | district of Rosenheim |
E226767
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Oberaudorf |
E430308
|
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: Oberaudorf | Statement: [district of Rosenheim, contains, Oberaudorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oberaudorf Context triple: [district of Rosenheim, contains, Oberaudorf]
-
A.
Oberaudorf
chosen
Oberaudorf is a small Bavarian town in southern Germany near the Austrian border, known for its alpine scenery and ski tourism.
-
B.
Oberdorf
Oberdorf is a Swiss municipality situated in the central alpine canton of Nidwalden.
-
C.
Oberdorf
Oberdorf is a locality within the Austrian municipality of Wolfurt in the state of Vorarlberg.
-
D.
Oberndorf am Neckar
Oberndorf am Neckar is a small town in the German state of Baden-Württemberg, historically known for its arms manufacturing industry.
-
E.
Oberweier
Oberweier is a district of the town of Gaggenau in the Rastatt district of Baden-Württemberg, Germany, known for its village character within the Murg Valley region.
- 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_69ca843280488190bc65600e843ef9e6 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd68c680e48190be82e3829e8711f0 |
completed | April 1, 2026, 6:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d139ce08ec81908a8e81c060667ac3 |
completed | April 4, 2026, 4:18 p.m. |
Created at: March 30, 2026, 7:47 p.m.