Triple

T4719806
Position Surface form Disambiguated ID Type / Status
Subject Yakutia E104734 entity
Predicate containsCity P294 FINISHED
Object Mirny E124388 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: Mirny | Statement: [Yakutia, containsCity, Mirny]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mirny
Context triple: [Yakutia, containsCity, Mirny]
  • A. Mirny chosen
    Mirny is a remote mining town in eastern Siberia best known for its massive open-pit diamond mine and role in Russia’s diamond industry.
  • B. Naryan-Mar
    Naryan-Mar is a small Arctic port city in northwestern Russia, serving as the administrative and economic center of the Nenets Autonomous Okrug.
  • C. Verkhoyansk
    Verkhoyansk is a small town in the Sakha Republic of Russia known as one of the coldest permanently inhabited places on Earth.
  • D. Mirny, Arkhangelsk Oblast
    Mirny, Arkhangelsk Oblast is a closed Russian town in northern European Russia that serves primarily as the administrative and residential center for personnel of the nearby Plesetsk Cosmodrome.
  • E. Pechenga
    Pechenga is a region in Russia’s far northwest, near the Barents Sea and the Norwegian border, historically known as Petsamo when it belonged to Finland.
  • 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_69bd43ec4a348190bc41afae43375e71 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6428e9e081908ce4041183cad13b completed March 20, 2026, 3:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69be39ff21f0819094a273a0f26b22f4 completed March 21, 2026, 6:26 a.m.
Created at: March 20, 2026, 1:18 p.m.