Triple
T20043580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rastatt district |
E497493
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Bühl |
—
|
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: Bühl | Statement: [Rastatt district, contains, Bühl]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bühl Context triple: [Rastatt district, contains, Bühl]
-
A.
Bühl
chosen
Bühl is a town in southwestern Germany’s Baden-Württemberg region, known for its fruit cultivation and proximity to the Black Forest.
-
B.
Steinbühl
Steinbühl is a district of the German city of Nuremberg, known as an urban residential area served by the Nürnberg-Steinbühl railway station.
-
C.
Sonnenbühl
Sonnenbühl is a municipality in the Swabian Alb region of Baden-Württemberg, Germany, known for its karst landscapes, caves, and outdoor recreation.
-
D.
Trostberg
Trostberg is a small Bavarian town in southeastern Germany known for its historic old town and chemical industry.
-
E.
Melchenbühl
Melchenbühl is a small locality within the municipality of Muri bei Bern in the canton of Bern, Switzerland.
- 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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e662ed59bc8190a9ff25493e500ebb |
completed | April 20, 2026, 5:31 p.m. |
Created at: April 11, 2026, 3:37 p.m.