Triple
T8572010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selzach |
E202947
|
entity |
| Predicate | sharesBorderWith |
P224
|
FINISHED |
| Object | Langendorf |
E166452
|
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: Langendorf | Statement: [Selzach, sharesBorderWith, Langendorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Langendorf Context triple: [Selzach, sharesBorderWith, Langendorf]
-
A.
Langendorf
chosen
Langendorf is a municipality in the canton of Solothurn in northwestern Switzerland.
-
B.
Dennewitz
Dennewitz is a village in Brandenburg, Germany, historically notable as the site of a major 1813 battle during the Napoleonic Wars.
-
C.
Wietzendorf
Wietzendorf is a small municipality in Lower Saxony, Germany, known for its rural character and location in the Lüneburg Heath region.
-
D.
Rüngsdorf
Rüngsdorf is a residential district in the southern part of Bonn, Germany, known for its scenic location along the Rhine and its affiliation with the Bad Godesberg borough.
-
E.
Neuendorf
Neuendorf is a small village on the Baltic Sea island of Hiddensee in Germany, known for its traditional thatched houses and maritime character.
- 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_69ca8327b0a881908606ff860713964d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbea43843c8190ac2224d427bb7a75 |
completed | March 31, 2026, 3:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf6ea4fadc8190ade74e4fdf890056 |
completed | April 3, 2026, 7:39 a.m. |
Created at: March 30, 2026, 6:21 p.m.