Triple
T10267711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval Education and Training Security Assistance Field Activity |
E240751
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | security assistance organization |
C6396
|
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: security assistance organization Context triple: [Naval Education and Training Security Assistance Field Activity, instanceOf, security assistance organization]
-
A.
cybersecurity agency
A cybersecurity agency is an organization that protects digital systems, networks, and data from cyber threats through monitoring, prevention, incident response, and security consulting.
-
B.
security service network
A security service network is an interconnected system of tools, protocols, and infrastructure designed to monitor, protect, and manage the security of digital assets and communications across distributed environments.
-
C.
security contractor
A security contractor is an independent professional or firm hired to plan, implement, and manage protective measures for people, property, information, or operations, often in high-risk or specialized environments.
-
D.
security agency
chosen
A security agency is an organization that provides professional protection, surveillance, and risk management services to safeguard people, property, and information.
-
E.
security partnership
A security partnership is a collaborative relationship between organizations, agencies, or nations to share resources, information, and responsibilities for preventing, detecting, and responding to security threats.
- 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_69d381a94c1881908fc38fc263d9b9c2 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:34 a.m.