Triple
T21645788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augst |
E534209
|
entity |
| Predicate | neighboringMunicipality |
P17964
|
FINISHED |
| Object | Frenkendorf |
—
|
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: Frenkendorf | Statement: [Augst, neighboringMunicipality, Frenkendorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Frenkendorf Context triple: [Augst, neighboringMunicipality, Frenkendorf]
-
A.
Frenkendorf
chosen
Frenkendorf is a municipality in the canton of Basel-Landschaft in northwestern Switzerland, located near the city of Basel.
-
B.
Bendorf
Bendorf is a town on the Rhine River in Rhineland-Palatinate, Germany, known for its industrial heritage and proximity to Koblenz.
-
C.
Gneixendorf
Gneixendorf is a village and cadastral community that forms part of the city of Krems an der Donau in Lower Austria.
-
D.
Uetendorf
Uetendorf is a municipality in the canton of Bern in Switzerland, located in the Thun administrative district.
-
E.
Plittersdorf
Plittersdorf is a village and district of the town of Rastatt in the state of Baden-Württemberg in southwestern Germany.
- 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_69e0c466aec88190ba39c7543dbc8ba2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef5394c570819081dbbe7e0f98f7d3 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 16, 2026, 6:35 p.m.