Triple

T34079571
Position Surface form Disambiguated ID Type / Status
Subject Akmolinsk Oblast (historical) E873995 entity
Predicate partOfEmpireRegion P197213 FINISHED
Object Russian Turkestan 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: Russian Turkestan | Statement: [Akmolinsk Oblast (historical), partOfEmpireRegion, Russian Turkestan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: partOfEmpireRegion
Context triple: [Akmolinsk Oblast (historical), partOfEmpireRegion, Russian Turkestan]
  • A. provinceOfEmpire chosen
    Indicates that a given province belongs to, is governed by, or forms an administrative part of a particular empire.
  • B. wasCoreTerritoryOf
    Indicates that a region historically formed the central or most important territorial area belonging to a particular political or cultural entity.
  • C. underColonialAdministrativeUnit
    Indicates that one entity functioned within the jurisdiction or authority of a specified colonial administrative unit.
  • D. westernPartOccupiedBy
    Indicates that the western portion of a region, area, or object is currently taken up, controlled, or inhabited by a specified entity.
  • E. regionOfDynasty
    Indicates the geographic region or area in which a given dynasty held power or was primarily based.
  • F. None of above.

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_69f349a566808190a1c63b898f33cddf completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_6a002ae74da08190a4b47e0ff0f7f8fe completed May 10, 2026, 6:51 a.m.
PD Predicate disambiguation batch_6a0029cc369c81909578e52c4a75ab18 completed May 10, 2026, 6:46 a.m.
Created at: May 1, 2026, 1:52 a.m.