Triple
T10870539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uri |
E256636
|
entity |
| Predicate | hasCity |
P316
|
FINISHED |
| Object | Altdorf |
E535017
|
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: Altdorf | Statement: [Uri, hasCity, Altdorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Altdorf Context triple: [Uri, hasCity, Altdorf]
-
A.
Altdorf
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.
Arzdorf
Arzdorf is a village and district of the municipality of Wachtberg in the Rhein-Sieg-Kreis region of North Rhine-Westphalia, Germany.
-
C.
Urdorf
Urdorf is a municipality in the canton of Zurich in Switzerland, located in the Limmat Valley near the city of Zurich.
-
D.
Altdorf (Landshut)
Altdorf (Landshut) is a municipality in Lower Bavaria, Germany, situated near the city of Landshut.
-
E.
Altdorf (Uri)
chosen
Altdorf (Uri) is a historic town in central Switzerland, known as the capital of the canton of Uri and closely associated with the William Tell legend.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7518610e48190bee50db71ae0ca3e |
completed | April 9, 2026, 7:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e154cc97f88190aef41d18b5ebe836 |
completed | April 16, 2026, 9:29 p.m. |
Created at: April 8, 2026, 9:20 p.m.