Triple
T13468402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorothy Wetzel Hunt |
E311564
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | CIA employee |
C29266
|
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: CIA employee Context triple: [Dorothy Wetzel Hunt, instanceOf, CIA employee]
-
A.
CIA official
chosen
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.
-
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.
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.
-
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.
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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:42 p.m.