Triple
T28301567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Police Field Force |
E713722
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | paramilitary police unit |
C859
|
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: paramilitary police unit Context triple: [Police Field Force, instanceOf, paramilitary police unit]
-
A.
paramilitary organization
chosen
A paramilitary organization is a structured group that operates with military-style training, hierarchy, and tactics but is not formally part of a recognized state's official armed forces.
-
B.
paramilitary air unit
A paramilitary air unit is a non-military aviation organization structured and equipped in a military-like manner to conduct security, surveillance, support, or combat-adjacent operations under civilian or semi-civilian authority.
-
C.
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.
-
D.
military unit
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
E.
special operations forces unit
A special operations forces unit is a highly trained, small military team designed to conduct specialized, high-risk missions such as reconnaissance, direct action, counterterrorism, and unconventional warfare, often in politically sensitive or denied environments.
- 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_69efb524ab688190a1ce7ee7c9520932 |
completed | April 27, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11:35 p.m.