Triple
T12501916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bladensburg Police Department |
E298846
|
entity |
| Predicate | policeDepartmentType |
P105319
|
FINISHED |
| Object | local police |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: local police | Statement: [Bladensburg Police Department, policeDepartmentType, local police]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policeDepartmentType Context triple: [Bladensburg Police Department, policeDepartmentType, local police]
-
A.
hasPoliceDepartment
Indicates that an entity possesses, is served by, or is administratively associated with a police department.
-
B.
policeBureau
Indicates that an entity functions as or is associated with a police bureau or police department.
-
C.
policePrecinct
Indicates that a specified location, building, or area functions as or is designated as a police precinct.
-
D.
cityDepartment
Indicates that one entity is a department that operates within, or is administratively part of, a particular city.
-
E.
policeUnit
Indicates that one entity is a police unit (such as a department, squad, or division) associated with or responsible for another entity.
- F. None of above. chosen
Provenance (4 batches)
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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e8a706c8190873623eab7db607d |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d41f3cc8190a3331fb9a895306f |
completed | April 10, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69d94e87e0e88190bc49dcfe4954c7e0 |
completed | April 10, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:57 p.m.