Triple
T22332430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parliamentary Protection Services |
E552055
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | parliamentary security unit |
C17129
|
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: parliamentary security unit Context triple: [Parliamentary Protection Services, instanceOf, parliamentary security unit]
-
A.
parliamentary security organization
chosen
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.
-
B.
People’s Armed Police unit
A People’s Armed Police unit is a paramilitary formation responsible for internal security, law enforcement support, and emergency response under the command structure of the People’s Armed Police force.
-
C.
presidential guard
A presidential guard is an elite security unit responsible for protecting the head of state, their residence, and key government facilities from internal and external threats.
-
D.
special weapons and tactics unit
A special weapons and tactics unit is a highly trained law enforcement team equipped and organized to handle high-risk operations such as hostage rescues, armed standoffs, and counterterrorism incidents beyond the capabilities of regular police patrols.
-
E.
Verteidigungsausschuss
Der Verteidigungsausschuss ist ein parlamentarisches Gremium, das die Verteidigungs- und Sicherheitspolitik eines Staates überwacht, Gesetzentwürfe im Verteidigungsbereich berät und die Arbeit des Verteidigungsministeriums kontrolliert.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:43 p.m.