Triple
T12055656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gams |
E287034
|
entity |
| Predicate | hasNeighboringMunicipality |
P224
|
FINISHED |
| Object | Vaduz |
E110866
|
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: Vaduz | Statement: [Gams, hasNeighboringMunicipality, Vaduz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vaduz Context triple: [Gams, hasNeighboringMunicipality, Vaduz]
-
A.
Vaduz
chosen
Vaduz is the small alpine town that serves as the political and cultural center of the Principality of Liechtenstein.
-
B.
Chur
Chur is the oldest town in Switzerland and the capital of the canton of Graubünden, known for its historic old town and role as a gateway to the Alps.
-
C.
Balzers
Balzers is a municipality in southern Liechtenstein known for its scenic Alpine setting and historic Gutenberg Castle.
-
D.
Landquart
Landquart is a river in eastern Switzerland that flows through the canton of Graubünden before joining the Alpine Rhine.
-
E.
Türnich
Türnich is a district of the town of Kerpen in North Rhine-Westphalia, Germany, known as a residential area within the Cologne metropolitan region.
- 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_69d6ab4780948190bdb9f7620c2ac27e |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90425258c8190ba7b3b837c439253 |
completed | April 10, 2026, 2:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f60a62f0fc8190a3d15ccfb23bb788 |
completed | May 2, 2026, 2:29 p.m. |
Created at: April 8, 2026, 9:47 p.m.