Triple
T5392785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feldbrunnen-St. Niklaus |
E120372
|
entity |
| Predicate | neighboringMunicipality |
P17964
|
FINISHED |
| Object | Riedholz |
E123873
|
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: Riedholz | Statement: [Feldbrunnen-St. Niklaus, neighboringMunicipality, Riedholz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Riedholz Context triple: [Feldbrunnen-St. Niklaus, neighboringMunicipality, Riedholz]
-
A.
Riedholz
chosen
Riedholz is a small Swiss municipality located in the canton of Solothurn.
-
B.
Emigholz
Emigholz is a German surname most notably associated with filmmaker and artist Heinz Emigholz.
-
C.
Plauen
Plauen is a historic town in eastern Germany known for its textile industry and intricate lace production.
-
D.
Französisch Buchholz
Französisch Buchholz is a northeastern locality of Berlin known for its village-like character and incorporation into the borough of Pankow.
-
E.
Bramsche
Bramsche is a town in Lower Saxony, Germany, known for its location near Osnabrück and its historical textile industry.
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd871b81d08190993928e2c6251226 |
completed | March 20, 2026, 5:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf336d43a081909ab05d237c297c7b |
completed | March 22, 2026, 12:10 a.m. |
Created at: March 20, 2026, 2:04 p.m.