Triple
T7586890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Administrative Services Division (Prince George’s County Police Department) |
E179635
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | police administrative division |
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: police administrative division Context triple: [Administrative Services Division (Prince George’s County Police Department), instanceOf, police administrative division]
-
A.
occupation authority division
Occupation authority division is the organizational structure and allocation of powers among governing bodies or agencies responsible for administering and controlling a territory under military or foreign occupation.
-
B.
police force
A police force is an organized body of officers empowered by a government to maintain public order, enforce laws, prevent and investigate crime, and protect citizens and property.
-
C.
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.
-
D.
military administrative division
A military administrative division is a geographically defined area organized under a specific command structure to manage, coordinate, and support military operations, logistics, and governance within its boundaries.
-
E.
district administration
District administration is the local governing and executive authority responsible for implementing government policies, managing public services, and coordinating development activities within a defined district.
- 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_69c69f335248819093c1006f30513708 |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 3:52 p.m.