Triple
T20456946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roberto Conesa |
E501815
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | secret police operative |
C29388
|
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 operative Context triple: [Roberto Conesa, instanceOf, secret police operative]
-
A.
criminal operative
A criminal operative is an individual who covertly plans, coordinates, or executes illegal activities—often within an organized network—while employing specialized skills to evade detection and law enforcement.
-
B.
former intelligence operative
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.
-
C.
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.
-
D.
Cheka officer
chosen
A Cheka officer is a member of the early Soviet secret police responsible for internal security, political repression, and the suppression of perceived enemies of the Bolshevik regime.
-
E.
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.
- 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_69e0b4ad4940819098cf2ff6413574e5 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:32 a.m.