Triple
T34648278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 24th Pct |
E889763
|
entity |
| Predicate | cityAgency |
P68320
|
FINISHED |
| Object | New York City Police Department |
—
|
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: New York City Police Department | Statement: [24th Pct, cityAgency, New York City Police Department]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityAgency Context triple: [24th Pct, cityAgency, New York City Police Department]
-
A.
cityDepartment
chosen
Indicates that one entity is a department that operates within, or is administratively part of, a particular city.
-
B.
cityAuthority
Indicates that an entity holds official governing or administrative authority over a city.
-
C.
cityGovernment
Indicates that a city’s governing authority has jurisdiction, control, or administrative responsibility over the referenced entity.
-
D.
cityService
Indicates that a service is provided by, operates within, or is administered by a particular city.
-
E.
districtAdministration
Indicates that an entity is responsible for managing, governing, or overseeing the administrative affairs of a specific district or local jurisdiction.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f72297b0348190b370585ac3c059c6 |
completed | May 3, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:04 a.m.