Triple
T35680055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronx Community District 3 |
E1030979
|
entity |
| Predicate | hasNYCCommunityDistrictCode |
P155105
|
FINISHED |
| Object | 203 |
—
|
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: 203 | Statement: [Bronx Community District 3, hasNYCCommunityDistrictCode, 203]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNYCCommunityDistrictCode Context triple: [Bronx Community District 3, hasNYCCommunityDistrictCode, 203]
-
A.
hasBoroughCommunityDistrictCode
chosen
Indicates that a borough is associated with a specific community district code that identifies one of its administrative subdivisions.
-
B.
hasCommunityDistrict
Indicates that an entity is located within, associated with, or falls under the jurisdiction of a specific community district.
-
C.
hasBoroughCode
Indicates that an entity is associated with a specific borough identified by a particular code.
-
D.
locatedInBoroughCommunityDistrict
Indicates that something is situated within a specific borough community district.
-
E.
communityDistrictNumber
Indicates the specific community district identifier associated with an entity or location.
- 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_69f76e0bb6608190ad3a1880be54a17d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79fe983d48190915b44d890293ab6 |
completed | May 3, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.