Triple
T9676628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polizia di Frontiera |
E234169
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | specialized branch of Polizia di Stato |
C3496
|
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: specialized branch of Polizia di Stato Context triple: [Polizia di Frontiera, instanceOf, specialized branch of Polizia di Stato]
-
A.
state police agency
A state police agency is a government law enforcement organization with statewide jurisdiction responsible for enforcing laws, maintaining public order, and supporting local agencies across the entire state.
-
B.
specialized operations division
A specialized operations division is a focused organizational unit responsible for planning and executing complex, high-priority, or technically advanced missions that fall outside the scope of standard operational teams.
-
C.
specialized wing of Border Security Force
A specialized wing of the Border Security Force is a dedicated unit with focused training, equipment, and operational mandates to address specific border security challenges such as counter-infiltration, intelligence gathering, or high-risk tactical operations.
-
D.
law enforcement unit
chosen
A law enforcement unit is an organized group within a policing or security agency tasked with enforcing laws, maintaining public order, and conducting specialized operations or investigations.
-
E.
specialized division
A specialized division is a distinct organizational unit focused on a specific function, expertise, or market segment to improve efficiency and effectiveness within a larger entity.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:16 p.m.