Triple
T15747544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Komitet do spraw Bezpieczeństwa Publicznego |
E381758
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish state security agency |
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 agency Context triple: [Komitet do spraw Bezpieczeństwa Publicznego, instanceOf, Polish state security agency]
-
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.
Polish military institution
A Polish military institution is an organization established by the Polish state to manage, train, support, or command elements of the armed forces in accordance with national defense policies and legal frameworks.
-
D.
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.
-
E.
British intelligence agency
A British intelligence agency is a government organization responsible for gathering, analyzing, and acting on information to protect the United Kingdom’s national security and interests at home and abroad.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:46 a.m.