Triple

T19472921
Position Surface form Disambiguated ID Type / Status
Subject Schaan-Vaduz railway station E487169 entity
Predicate locatedIn P40 FINISHED
Object Schaan 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: Schaan | Statement: [Schaan-Vaduz railway station, locatedIn, Schaan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schaan
Context triple: [Schaan-Vaduz railway station, locatedIn, Schaan]
  • A. Schaan chosen
    Schaan is a major municipality in Liechtenstein known as its principal urban and industrial center.
  • B. Ruggell
    Ruggell is a northern Liechtenstein municipality known for its flat Rhine valley landscape and agricultural character.
  • C. Dudelange
    Dudelange is a town in southern Luxembourg known as one of the country’s larger industrial and residential centers near the French border.
  • D. Differdange
    Differdange is a town in southwestern Luxembourg known as an industrial center with a strong steelmaking heritage.
  • E. Schafhausen
    Schafhausen is a village and district of the town Weil der Stadt in the German state of Baden-Württemberg.
  • 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_69d8e8d924388190b847cb15bb3d0aff completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e633ea604c8190a2feacb709b7ca27 completed April 20, 2026, 2:10 p.m.
Created at: April 10, 2026, 1:39 p.m.