Triple
T11630370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leonding |
E276379
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Hörsching |
E569714
|
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: Hörsching | Statement: [Leonding, borderedBy, Hörsching]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hörsching Context triple: [Leonding, borderedBy, Hörsching]
-
A.
Hörsching
chosen
Hörsching is a municipality in Upper Austria, best known for hosting Linz Airport and lying near the city of Linz.
-
B.
Geiselhöring
Geiselhöring is a small town in Lower Bavaria, Germany, known for its rural character and location within the Straubing-Bogen district.
-
C.
Schiltach
Schiltach is a small historic town in Germany’s Black Forest region, known for its well-preserved half-timbered houses and picturesque riverside setting.
-
D.
Kirchlindach
Kirchlindach is a Swiss municipality in the canton of Bern, known for its rural character and proximity to the city of Bern.
-
E.
Eschbach
Eschbach is a village and district of the town of Usingen in the Hochtaunus region of Hesse, Germany.
- 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_69d8a127b2688190ae3a340f851e834b |
completed | April 10, 2026, 7:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ef135cde4881908d1cf9f752592d60 |
completed | April 27, 2026, 7:42 a.m. |
Created at: April 8, 2026, 9:39 p.m.