Triple

T5360340
Position Surface form Disambiguated ID Type / Status
Subject Democratic Republic of Afghanistan E103004 entity
Predicate instanceOf P0 FINISHED
Object Soviet-aligned state C18009 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: Soviet-aligned state
Context triple: [Democratic Republic of Afghanistan, instanceOf, Soviet-aligned state]
  • A. 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.
  • B. socialist republic
    A socialist republic is a state governed as a republic in which political power and key means of production are formally organized and managed according to socialist principles, typically emphasizing public ownership, economic planning, and social welfare.
  • C. Russian state
    The Russian state is a centralized political entity that exercises sovereign authority over the territory and population of Russia through its institutions of governance, law, security, and administration.
  • D. Soviet organization
    A Soviet organization is an institution, agency, or collective entity established under the governance and ideological framework of the Soviet Union to manage political, economic, social, or military functions.
  • E. constituent republic of Yugoslavia
    A constituent republic of Yugoslavia was a federal unit within the Socialist Federal Republic of Yugoslavia that possessed its own government and constitution while remaining subordinate to the federal authorities.
  • 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_69bd43daa3e4819090b59d127db70e57 completed March 20, 2026, 12:55 p.m.
Created at: March 20, 2026, 2:02 p.m.