Triple
T9805120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government Protection Bureau |
E237935
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish state security service |
C3363
|
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: Polish state security service Context triple: [Government Protection Bureau, instanceOf, Polish state security service]
-
A.
government agency of Poland
A government agency of Poland is an official public institution established by the Polish state to perform specific administrative, regulatory, or service functions on behalf of the government.
-
B.
Polish resistance organization
A Polish resistance organization is a clandestine group formed in Poland to oppose and undermine occupying or oppressive regimes through coordinated political, military, and intelligence activities.
-
C.
state security agency
chosen
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.
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.
interior ministry
The interior ministry is a government department responsible for domestic affairs, including internal security, public administration, civil registration, and often oversight of police and emergency services.
- 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.