Triple

T9006416
Position Surface form Disambiguated ID Type / Status
Subject Mikhail Borodin E215153 entity
Predicate instanceOf P0 FINISHED
Object Comintern agent C12229 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: Comintern agent
Context triple: [Mikhail Borodin, instanceOf, Comintern agent]
  • A. Soviet agent chosen
    A Soviet agent is an individual who covertly gathers, transmits, or influences information and activities on behalf of the Soviet state’s intelligence or security services, often operating under false identities or clandestine arrangements.
  • B. Special Operations Executive agent
    A Special Operations Executive agent is a covert operative trained to conduct sabotage, espionage, and support for resistance movements behind enemy lines during wartime.
  • C. Indian agent
    An Indian agent is a government-appointed official historically responsible for managing relations, negotiations, and administrative affairs between a colonial or federal authority and Indigenous or Native American tribes.
  • D. NKVD officer
    An NKVD officer is a member of the Soviet Union’s internal security and secret police organization responsible for intelligence, political repression, and enforcement of state control during the Stalinist era.
  • E. Confederate agent
    A Confederate agent is an individual who covertly gathered intelligence, conducted sabotage, or engaged in clandestine operations in support of the Confederate States during the American Civil War.
  • 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_69ca83a12d648190b1e4fe11e8a31890 completed March 30, 2026, 2:07 p.m.
Created at: March 30, 2026, 7:05 p.m.