Triple

T21777899
Position Surface form Disambiguated ID Type / Status
Subject Astana–Almaty E537628 entity
Predicate cityStatusOfAstana P22389 FINISHED
Object capital of Kazakhstan LITERAL 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: capital of Kazakhstan | Statement: [Astana–Almaty, cityStatusOfAstana, capital of Kazakhstan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: cityStatusOfAstana
Context triple: [Astana–Almaty, cityStatusOfAstana, capital of Kazakhstan]
  • A. cityStatusContext chosen
    Indicates the contextual status or role that a city holds within a broader administrative, political, or situational framework.
  • B. independentCityStatus
    Indicates that a city functions as an administratively independent entity, not subordinated to a surrounding regional or local government unit.
  • C. cityStatusUntil
    Indicates the period up to a specified time during which a place holds or held a particular city status.
  • D. cityCenterStatus
    Indicates whether a location holds the status of being the central or main area of a city.
  • E. cityStatusGrantedBy
    Indicates that one entity (such as a person, authority, or institution) formally granted or conferred city status upon another entity (typically a settlement or locality).
  • 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_69e0c470759c819094a215757113562b completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f0462b094c81908207073c278a58fe completed April 28, 2026, 5:31 a.m.
PD Predicate disambiguation batch_69e6be6299988190a34c98fa76d94700 completed April 21, 2026, 12:01 a.m.
Created at: April 16, 2026, 6:51 p.m.