Triple
T38497117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NYPD 103rd Precinct |
E919723
|
entity |
| Predicate | sectorPatrolModel |
P116371
|
FINISHED |
| Object | NYPD neighborhood coordination officers (NCOs) |
—
|
NE NERFINISHED |
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: NYPD neighborhood coordination officers (NCOs) | Statement: [NYPD 103rd Precinct, sectorPatrolModel, NYPD neighborhood coordination officers (NCOs)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectorPatrolModel Context triple: [NYPD 103rd Precinct, sectorPatrolModel, NYPD neighborhood coordination officers (NCOs)]
-
A.
patrolsWith
Indicates that two or more entities conduct a patrol together as a coordinated or joint activity.
-
B.
patrolType
chosen
Indicates the specific kind or category of patrol activity being carried out or assigned.
-
C.
patrolledBy
Indicates that an area, route, or domain is regularly monitored or guarded by a specific agent or group.
-
D.
patrolMethod
Indicates the method or manner in which a patrol is conducted or carried out.
-
E.
policeSystem
Indicates a relationship where an entity functions as, belongs to, or is governed by a system of law enforcement or policing.
- 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_69f76e9ddd4481908f8c04439d848f9d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.