Triple
T3709826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urząd Bezpieczeństwa |
E80981
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish secret police |
C3179
|
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 secret police Context triple: [Urząd Bezpieczeństwa, instanceOf, Polish secret police]
-
A.
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.
-
B.
Soviet agent
A Soviet agent is an individual who covertly gathers, transmits, or influences information and activities on behalf of the Soviet state’s intelligence or security services, often operating under false identities or clandestine arrangements.
-
C.
interior ministry
chosen
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.
-
D.
institution of the Polish government-in-exile
An institution of the Polish government-in-exile is an official body established by the displaced Polish state during and after World War II to represent Poland’s sovereignty, administer its affairs abroad, and coordinate political, military, and diplomatic efforts until a legitimate domestic government could be restored.
-
E.
polis
A polis is an ancient Greek city-state, functioning as an independent political, social, and religious community centered on an urban core and its surrounding territory.
- 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_69ad8b1793888190a5f70e4b21dc05a1 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:33 p.m.