Triple

T18263258
Position Surface form Disambiguated ID Type / Status
Subject Crimean Oblast E437415 entity
Predicate instanceOf P0 FINISHED
Object subdivision of the Russian SFSR C25064 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: subdivision of the Russian SFSR
Context triple: [Crimean Oblast, instanceOf, subdivision of the Russian SFSR]
  • A. former subdivision of the Russian Empire
    A former subdivision of the Russian Empire is an obsolete administrative-territorial unit that once functioned as part of the empire’s governmental structure but no longer exists in its original form.
  • B. oblast of the Russian SFSR chosen
    An oblast of the Russian SFSR was a primary administrative-territorial unit within the Russian Soviet Federative Socialist Republic, functioning as a regional level of government under the Soviet federal system.
  • C. constituent republic of the Soviet Union
    A constituent republic of the Soviet Union was a nominally sovereign national republic that, while having its own government and constitution, was politically and economically subordinate to the central Soviet federal authority.
  • D. district of Russia
    A district of Russia is an administrative subdivision within a federal subject that manages local governance, public services, and regional implementation of national laws for its constituent settlements.
  • E. autonomous okrug of Russia
    An autonomous okrug of Russia is a type of federal subject with a degree of self-governance, typically established in areas with significant indigenous or ethnic minority populations and often administratively associated with a larger region or krai.
  • F. None of above.

Provenance (1 batch)

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_69d8b913351c8190932b6a426de04b41 completed April 10, 2026, 8:47 a.m.
Created at: April 10, 2026, 10:34 a.m.