Triple

T18560237
Position Surface form Disambiguated ID Type / Status
Subject Nikolskoye E453616 entity
Predicate hasNameInLanguage P15 FINISHED
Object Никольское 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: Никольское | Statement: [Nikolskoye, hasNameInLanguage, Никольское]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Никольское
Context triple: [Nikolskoye, hasNameInLanguage, Никольское]
  • A. Nikolskoye
    Nikolskoye is the main and only permanent settlement on Russia’s remote Commander Islands in the Bering Sea.
  • B. Nikolskoye
    Nikolskoye is a town in northwestern Russia known as part of the Saint Petersburg metropolitan area in Leningrad Oblast.
  • C. Kastornoye
    Kastornoye is a locality in Russia historically notable as the namesake and focal area of the Voronezh–Kastornoye military offensive during World War II.
  • D. Vyatskoye
    Vyatskoye is a rural locality in Russia’s Khabarovsk Krai, historically noted as the birthplace of North Korean leader Kim Jong Il.
  • E. Kryukovo
    Kryukovo is a railway station and suburban district in Zelenograd, Moscow, serving as a key commuter hub on the Leningradsky suburban rail line.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide. chosen

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_69d8d388b0c881908e610a1c45b52640 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e538098a148190b0fc7098ce3c62fd completed April 19, 2026, 8:16 p.m.
Created at: April 10, 2026, 11:42 a.m.