Triple
T25013063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NYPD 110th Precinct |
E626048
|
entity |
| Predicate | policeCode |
P25037
|
FINISHED |
| Object | 110 |
—
|
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: 110 | Statement: [NYPD 110th Precinct, policeCode, 110]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policeCode Context triple: [NYPD 110th Precinct, policeCode, 110]
-
A.
policePackageCode
Indicates that an entity is associated with a specific police package code, typically identifying a law-enforcement-related configuration, option, or classification.
-
B.
policeNumber
chosen
Indicates that an entity is associated with a specific police-related identification or reference number.
-
C.
policeNumberingSystem
Indicates a system by which police assign and manage identification numbers to cases, incidents, or personnel.
-
D.
policeSystem
Indicates a relationship where an entity functions as, belongs to, or is governed by a system of law enforcement or policing.
-
E.
policePrecinct
Indicates that a specified location, building, or area functions as or is designated as a police precinct.
- F. None of above.
Provenance (3 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_69e2ff27755881908490178e83701160 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44ba3150c819090e7de4644429074 |
completed | May 1, 2026, 6:43 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:05 a.m.