Triple
T29551424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikhail Babich |
E749776
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former security service officer |
C35117
|
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: former security service officer Context triple: [Mikhail Babich, instanceOf, former security service officer]
-
A.
former intelligence operative
chosen
A former intelligence operative is an individual who previously worked in covert information-gathering, analysis, or clandestine operations for a government or private intelligence organization and has since left active service.
-
B.
former CIA officer
A former CIA officer is an individual who previously served in the Central Intelligence Agency, typically involved in intelligence collection, analysis, or covert operations, but is no longer actively employed by the agency.
-
C.
former FBI agent
A former FBI agent is an individual who previously served in the Federal Bureau of Investigation, typically possessing investigative, analytical, and law enforcement expertise gained from that role.
-
D.
former intelligence contractor
A former intelligence contractor is an individual who previously worked, typically on a temporary or project basis, for a government or intelligence agency providing specialized services or expertise related to intelligence operations, analysis, or support.
-
E.
former bodyguard
A former bodyguard is an individual who previously worked professionally to protect clients from physical harm or threats, often drawing on specialized security training and experience.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 5:12 p.m.