Triple
T973277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Personnel Bureau |
E20991
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | division of the New York City Police Department |
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: division of the New York City Police Department Context triple: [Personnel Bureau, instanceOf, division of the New York City Police Department]
-
A.
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.
-
B.
division of the United States Capitol Police
A division of the United States Capitol Police is an organizational unit within the agency responsible for specific protective, law enforcement, or administrative functions related to safeguarding the U.S. Capitol complex and its occupants.
-
C.
New York City community board
A New York City community board is a local advisory group of appointed residents that consults on land use, budget, and service delivery issues within a specific community district.
-
D.
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.
-
E.
borough of New York City
A borough of New York City is one of the five primary administrative and geographic divisions of the city, each coextensive with a county and possessing its own local identity, governance structures, and community characteristics within the larger metropolis.
- 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:40 p.m.