Triple
T18046161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rheingau-Taunus-Kreis |
E431777
|
entity |
| Predicate | containsMunicipality |
P852
|
FINISHED |
| Object | Lorch |
—
|
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: Lorch | Statement: [Rheingau-Taunus-Kreis, containsMunicipality, Lorch]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lorch Context triple: [Rheingau-Taunus-Kreis, containsMunicipality, Lorch]
-
A.
Lorch
chosen
Lorch is a historic town on the Upper Middle Rhine in Germany, known for its medieval architecture, winegrowing tradition, and scenic location along the Rhine Gorge.
-
B.
Tapfheim
Tapfheim is a small municipality in the Donau-Ries district of Bavaria in southern Germany.
-
C.
Herisau
Herisau is a Swiss town that serves as the administrative and economic center of the canton of Appenzell Ausserrhoden.
-
D.
Lauterach
Lauterach is a municipality in the Austrian state of Vorarlberg, located in the district of Bregenz near the Rhine Valley.
-
E.
Lauterach
Lauterach is a small municipality in the Alb-Donau district of Baden-Württemberg in southern Germany, known for its rural character and scenic Swabian Jura surroundings.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4bff202088190ae971879348e2294 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 10:25 a.m.