Triple
T21535046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A2 (Swiss motorway) |
E531328
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Altdorf |
—
|
NE NERFINISHED |
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: Altdorf | Statement: [A2 (Swiss motorway), passesThrough, Altdorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Altdorf Context triple: [A2 (Swiss motorway), passesThrough, Altdorf]
-
A.
Altdorf
chosen
Altdorf is a Swiss town in the canton of Uri, known as a historic transit point through the Alps and its association with the William Tell legend.
-
B.
Altdorf
Altdorf is a village in the Ortenau district of Baden-Württemberg, Germany, known as one of the local subdivisions of the town of Ettenheim.
-
C.
Arzdorf
Arzdorf is a village and district of the municipality of Wachtberg in the Rhein-Sieg-Kreis region of North Rhine-Westphalia, Germany.
-
D.
Urdorf
Urdorf is a municipality in the canton of Zurich in Switzerland, located in the Limmat Valley near the city of Zurich.
-
E.
Gnodstadt
Gnodstadt is a small village in Bavaria, Germany, that forms part of the town of Marktbreit in the Kitzingen district.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c45e5b8881908ac18fc2f493b114 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee9d0ce8d08190b3233d7117a9b1ca |
completed | April 26, 2026, 11:17 p.m. |
Created at: April 16, 2026, 6:27 p.m.