Triple

T22604984
Position Surface form Disambiguated ID Type / Status
Subject Sursilvan E566530 entity
Predicate closelyRelatedTo P37 FINISHED
Object Surmiran 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: 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. Gormati
    Gormati is the traditional language spoken by the Banjara people, a nomadic community in India known for its distinct culture and heritage.
  • D. Maselheim
    Maselheim is a rural municipality in the district of Biberach in the federal state of Baden-Württemberg in southern Germany.
  • E. Sormitz
    The Sormitz is a river in Thuringia, Germany, known for flowing through towns such as Leutenberg before joining the Saale.
  • 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_69e245884860819081046ce07d5872c4 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f162709d808190af83837104a190f9 completed April 29, 2026, 1:44 a.m.
Created at: April 17, 2026, 2:53 p.m.