Triple

T36450359
Position Surface form Disambiguated ID Type / Status
Subject Ayshe Seytmuratova E897991 entity
Predicate instanceOf P0 FINISHED
Object Crimean Tatar activist C64306 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: Crimean Tatar activist
Context triple: [Ayshe Seytmuratova, instanceOf, Crimean Tatar activist]
  • A. Uzbekistani human rights activist
    An Uzbekistani human rights activist is an individual from Uzbekistan who advocates for the protection and promotion of civil, political, social, and cultural rights, often challenging government abuses and working to advance legal and social reforms.
  • B. Ukrainian independence activist
    A Ukrainian independence activist is an individual who actively advocates, organizes, and mobilizes support for Ukraine’s political sovereignty, territorial integrity, and self-determination against foreign domination or influence.
  • C. Belarusian dissident
    A Belarusian dissident is an individual from Belarus who actively opposes the country's authoritarian government, often engaging in political activism, protest, or independent expression despite the risk of repression, imprisonment, or exile.
  • D. Romanian dissident
    A Romanian dissident is an individual who actively opposes and challenges Romania’s authoritarian or oppressive political regimes, often at personal risk, through protest, criticism, or resistance activities.
  • E. Crimean Tatar organization
    A Crimean Tatar organization is a formal group or institution established by or for Crimean Tatars to represent their interests, preserve their culture and language, and address social, political, or community issues.
  • F. None of above. chosen

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_69f76e5720b481908f8177ac24a7560b completed May 3, 2026, 3:48 p.m.
Created at: May 3, 2026, 4:10 p.m.