Triple
T25752447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CIA Technical Services Staff |
E648502
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | covert operations support unit |
C21092
|
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: covert operations support unit Context triple: [CIA Technical Services Staff, instanceOf, covert operations support unit]
-
A.
special operations support unit
chosen
A special operations support unit is a specialized organization that provides logistical, intelligence, technical, and operational assistance to special operations forces to enable and sustain their missions.
-
B.
covert operative
A covert operative is a highly trained individual who conducts secret missions and gathers sensitive information while maintaining a concealed identity and minimizing detection.
-
C.
special operations forces unit
A special operations forces unit is a highly trained, small military team designed to conduct specialized, high-risk missions such as reconnaissance, direct action, counterterrorism, and unconventional warfare, often in politically sensitive or denied environments.
-
D.
covert intelligence organization
A covert intelligence organization is a secretive entity that gathers, analyzes, and acts on sensitive information through clandestine methods to influence or protect national or organizational interests.
-
E.
military special operations command
A military special operations command is a specialized organizational unit responsible for planning, directing, and executing high-risk, strategically critical missions using elite, highly trained forces.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 4:36 a.m.