Triple
T5020066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genrikh Yagoda |
E112828
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | secret police official |
C10057
|
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: secret police official Context triple: [Genrikh Yagoda, instanceOf, secret police official]
-
A.
secret government agency
A secret government agency is a covert, officially sanctioned organization that operates outside public scrutiny to conduct sensitive intelligence, security, or special operations in the interest of national or global objectives.
-
B.
government informant
A government informant is an individual who secretly provides information or intelligence to a government agency about persons, organizations, or activities, often to support investigations or national security efforts.
-
C.
director of intelligence agency
A director of an intelligence agency is the top executive responsible for overseeing intelligence operations, setting strategic priorities, managing resources, and advising national leaders on security threats and information.
-
D.
Soviet agent
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.
-
E.
police officer
chosen
A police officer is a law enforcement professional responsible for maintaining public order, preventing and investigating crimes, and protecting the safety and rights of individuals within a community.
- 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_69bd4435c2f48190be593158cbfcf8a3 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:36 p.m.