Triple

T6073450
Position Surface form Disambiguated ID Type / Status
Subject Sursilvan E135340 entity
Predicate closelyRelatedTo P37 FINISHED
Object Surmiran E124253 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: Surmiran | Statement: [Sursilvan, closelyRelatedTo, Surmiran]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Surmiran
Context triple: [Sursilvan, closelyRelatedTo, Surmiran]
  • A. Surmiran chosen
    Surmiran is one of the main dialects of the Romansh language, traditionally spoken in the central region of the Swiss canton of Graubünden.
  • B. Soligalich
    Soligalich is a historic Russian town known for its preserved 18th–19th century architecture and location along the Kostroma River in Kostroma Oblast.
  • C. Reinswald
    Reinswald is a small alpine village and ski resort located in the Sarntal Alps of South Tyrol in northern Italy.
  • D. Šurany
    Šurany is a small town in southwestern Slovakia known for its agricultural surroundings and historical roots in the Nitra region.
  • E. Kimry
    Kimry is a small Russian town on the Volga River known historically for its shoemaking industry and wooden 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_69c00879e8048190b690717d19c5bc03 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c0575b9bc08190a78b3082b9ccf00c completed March 22, 2026, 8:55 p.m.
NED1 Entity disambiguation (via context triple) batch_69c11d3fb99481909cc31c179eb4e8c9 completed March 23, 2026, 11 a.m.
Created at: March 22, 2026, 4:11 p.m.