Triple

T5025448
Position Surface form Disambiguated ID Type / Status
Subject Schaan E112963 entity
Predicate neighboringMunicipality P17964 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: [Schaan, neighboringMunicipality, Vaduz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vaduz
Context triple: [Schaan, neighboringMunicipality, 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. Bregenz
    Bregenz is an Austrian city on the eastern shore of Lake Constance, known for its lakeside setting, cultural festivals, and contemporary art and architecture.
  • 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_69bd4435c2f48190be593158cbfcf8a3 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd736a0f8c819091d06275954329e9 completed March 20, 2026, 4:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69be9c60de2c81908208f93a4bd0ce55 completed March 21, 2026, 1:25 p.m.
Created at: March 20, 2026, 1:36 p.m.