Triple
T9805151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Protection Service of Poland |
E237936
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | protective security agency |
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: protective security agency Context triple: [State Protection Service of Poland, instanceOf, protective security agency]
-
A.
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.
-
B.
security agency
chosen
A security agency is an organization that provides professional protection, surveillance, and risk management services to safeguard people, property, and information.
-
C.
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.
-
D.
parliamentary security organization
A parliamentary security organization is a specialized body responsible for protecting the legislature’s members, staff, visitors, facilities, and information while supporting the safe and orderly conduct of parliamentary business.
-
E.
public safety agency
A public safety agency is an organization responsible for protecting the public from threats and hazards by preventing, responding to, and managing emergencies, crimes, and disasters within a community or jurisdiction.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:29 p.m.