Triple
T11623260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blaubeuren |
E276192
|
entity |
| Predicate | isPopularFor |
P22
|
FINISHED |
| Object | Blautopf spring |
E423255
|
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: Blautopf spring | Statement: [Blaubeuren, isPopularFor, Blautopf spring]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Blautopf spring Context triple: [Blaubeuren, isPopularFor, Blautopf spring]
-
A.
Blautopf spring
chosen
Blautopf spring is a strikingly blue karst spring and popular natural landmark near the town of Blaubeuren in Germany.
-
B.
Fraubrunnen
Fraubrunnen is a municipality in the canton of Bern in Switzerland, known for its rural character and location in the Swiss Plateau.
-
C.
Röthbachfall
Röthbachfall is a spectacular high waterfall in the Berchtesgaden Alps of Bavaria, Germany, renowned as one of the country's tallest and most scenic falls.
-
D.
Springpfuhl
Springpfuhl is a railway station in Berlin, Germany, serving the S-Bahn suburban rail network.
-
E.
Feldbrunnen
Feldbrunnen is a village and municipality in the canton of Solothurn in northwestern Switzerland.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a122a3708190ab6513dad4c4fde7 |
completed | April 10, 2026, 7:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ef13491c0c819085f4ea17ad74612a |
completed | April 27, 2026, 7:42 a.m. |
Created at: April 8, 2026, 9:39 p.m.