Triple
T31155293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Binney |
E794187
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former intelligence official |
C60968
|
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 intelligence official Context triple: [William Binney, instanceOf, former intelligence official]
-
A.
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.
-
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.
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.
-
D.
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.
-
E.
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.
- F. None of above. chosen
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_69f224d41bb48190a5621cd1485e3a30 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:06 p.m.