Triple
T786661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of Policy Coordination |
E16817
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | covert government organization |
C3529
|
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 government organization Context triple: [Office of Policy Coordination, instanceOf, covert government organization]
-
A.
covert intelligence organization
chosen
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.
-
B.
governmental organization
A governmental organization is a formally structured public entity established by a government to create, implement, or enforce laws, policies, and services for a specific jurisdiction or public purpose.
-
C.
state security agency
A state security agency is a government organization responsible for protecting national security through intelligence gathering, counterintelligence, and enforcement activities aimed at preventing internal and external threats.
-
D.
paramilitary organization
A paramilitary organization is a structured group that operates with military-style training, hierarchy, and tactics but is not formally part of a recognized state's official armed forces.
-
E.
federation of government agencies
A federation of government agencies is a collaborative structure in which multiple semi-autonomous public organizations coordinate policies, resources, and operations to achieve shared governmental objectives while retaining their individual mandates.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:38 p.m.