Triple
T9540651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regen (district) |
E230146
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Bodenmais |
E813687
|
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: Bodenmais | Statement: [Regen (district), contains, Bodenmais]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bodenmais Context triple: [Regen (district), contains, Bodenmais]
-
A.
Bodenmais
chosen
Bodenmais is a Bavarian spa and holiday resort town in the Bavarian Forest of Germany, known for its glassmaking tradition and outdoor recreation.
-
B.
Todenfeld
Todenfeld is a village and district of the town of Rheinbach in the Rhein-Sieg-Kreis region of North Rhine-Westphalia, Germany.
-
C.
Gerlosbach
Gerlosbach is a mountain river in Tyrol, Austria, that flows through the Zillertal Alps before joining the Ziller.
-
D.
Landensberg
Landensberg is a small municipality in the Bavarian region of southern Germany.
-
E.
Seckbach
Seckbach is a district in the east of Frankfurt am Main, Germany, known for its residential character and proximity to green spaces like the Lohrberg.
- 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_69ca847b1b3081908f72bc932c17cc41 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98e695948190ab107fff38c57de7 |
completed | April 1, 2026, 10:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19f60aa508190b3966f4b917c41b5 |
completed | April 4, 2026, 11:31 p.m. |
Created at: March 30, 2026, 8:01 p.m.