Triple
T8259663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lech Bridge at Füssen |
E193160
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Füssen |
E372327
|
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: Füssen | Statement: [Lech Bridge at Füssen, locatedIn, Füssen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Füssen Context triple: [Lech Bridge at Füssen, locatedIn, Füssen]
-
A.
Füssen
chosen
Füssen is a picturesque Bavarian town in southern Germany, known for its historic old town, proximity to Neuschwanstein Castle, and scenic location near the Alps.
-
B.
Kempten
Kempten is a historic town in Bavaria, Germany, considered one of the country’s oldest urban settlements and known for its location in the Allgäu region.
-
C.
Rosenheim
Rosenheim is a town in Upper Bavaria, Germany, known as a regional economic and transportation hub near the Alps.
-
D.
Wolfratshausen
Wolfratshausen is a Bavarian town in southern Germany known for its historic old town, riverside setting on the Loisach and Isar, and proximity to Munich and the Alps.
-
E.
Traunstein
Traunstein is a town in southeastern Bavaria, Germany, known as a regional administrative and cultural center near the Chiemsee and the Alps.
- 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb793479d08190bd0dd8740bebff95 |
completed | March 31, 2026, 7:35 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cffd4c307881909996adedc959180f |
completed | April 3, 2026, 5:47 p.m. |
Created at: March 30, 2026, 5:49 p.m.