Triple
T15330688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linz Airport |
E366523
|
entity |
| Predicate | locatedIn |
P40
|
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: [Linz Airport, locatedIn, Hörsching]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hörsching Context triple: [Linz Airport, locatedIn, 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.
Uttenreuth
Uttenreuth is a small municipality in Bavaria, Germany, situated near the city of Erlangen.
-
D.
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.
-
E.
Kirchlindach
Kirchlindach is a Swiss municipality in the canton of Bern, known for its rural character and proximity to the city of Bern.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e0161ac8190aa1d52c063c02ad0 |
completed | April 16, 2026, 1:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fef8b1b2d08190a158bf65535ad750 |
completed | May 9, 2026, 9:04 a.m. |
Created at: April 10, 2026, 3:17 a.m.