Triple
T14888162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Günterstalbach |
E359681
|
entity |
| Predicate | hasNameComponent |
P24447
|
FINISHED |
| Object | Günterstal |
E1134507
|
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: Günterstal | Statement: [Günterstalbach, hasNameComponent, Günterstal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Günterstal Context triple: [Günterstalbach, hasNameComponent, Günterstal]
-
A.
Günterstal
chosen
Günterstal is a district of Freiburg im Breisgau in southwestern Germany, known for its scenic valley setting in the Black Forest and historic monastery.
-
B.
Haslach
Haslach is a district or locality that forms part of the town of Oberkirch in the German state of Baden-Württemberg.
-
C.
Haslach
Haslach is a town in southern Germany historically noted as the site of the Battle of Haslach-Jungingen during the Napoleonic Wars.
-
D.
Fuchstal
Fuchstal is a municipality in the Bavarian region of Germany, known for its rural character and location within the district of Weilheim-Schongau.
-
E.
Geiersthal
Geiersthal is a small municipality in the Bavarian Forest region of southeastern Germany.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded5f6cf5c8190b6b28f58fafe5d59 |
completed | April 15, 2026, 12:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feae005644819098937cedb53202c5 |
completed | May 9, 2026, 3:46 a.m. |
Created at: April 10, 2026, 2:08 a.m.