Triple
T19785594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | district of Rastatt |
E475255
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | town of 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: town of Bühl | Statement: [district of Rastatt, contains, town of Bühl]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: town of Bühl Context triple: [district of Rastatt, contains, town of 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.
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.
-
C.
town of Lübz
The town of Lübz is a small historic municipality in the German state of Mecklenburg-Vorpommern, known for its traditional architecture and regional brewery.
-
D.
Böhlen
Böhlen is a small town in the Leipzig district of Saxony, Germany, known for its lignite mining and power generation industries.
-
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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65387d3348190a31f9c2f9bc1c6d9 |
completed | April 20, 2026, 4:25 p.m. |
Created at: April 10, 2026, 1:49 p.m.