Triple
T16781031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Reese |
E407856
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former CIA operative |
C24663
|
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 CIA operative Context triple: [John Reese, instanceOf, former CIA operative]
-
A.
former CIA officer
chosen
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.
-
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.
CIA official
A CIA official is a government intelligence professional responsible for overseeing, coordinating, or executing activities related to the collection, analysis, and protection of sensitive national security information.
-
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.
CIA security contractor
A CIA security contractor is a private-sector professional or firm hired by the Central Intelligence Agency to provide specialized security, protection, and risk management services in support of intelligence operations and facilities.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:22 a.m.