Triple

T10284056
Position Surface form Disambiguated ID Type / Status
Subject Mtsensky Uyezd E241180 entity
Predicate centralSettlement P18768 FINISHED
Object Mtsensk E847866 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: Mtsensk | Statement: [Mtsensky Uyezd, centralSettlement, Mtsensk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mtsensk
Context triple: [Mtsensky Uyezd, centralSettlement, Mtsensk]
  • A. Mtsensk chosen
    Mtsensk is a historic town in western Russia known for its literary associations and role as a local industrial and cultural center.
  • B. Zaraysk
    Zaraysk is a historic town in Moscow Oblast, Russia, known for its well-preserved medieval kremlin and role as a former regional administrative center.
  • C. Pervouralsk
    Pervouralsk is an industrial city in Russia’s Ural region, known for its metallurgical plants and location near the geographic border between Europe and Asia.
  • D. Votkinsk
    Votkinsk is a Russian town in Udmurtia best known as the birthplace of composer Pyotr Ilyich Tchaikovsky.
  • E. Nevyansk
    Nevyansk is a historic town in Russia’s Ural region, best known for its 18th-century Leaning Tower of Nevyansk and its role in early Russian industrial development.
  • 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_69d381aaafc08190af475ef58dc16aba completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d2b5853081909cd0397e08a0f44d completed April 7, 2026, 9:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69dbac97ce2481908ea11d6290a9bf2f completed April 12, 2026, 2:30 p.m.
Created at: April 6, 2026, 11:39 a.m.