Triple
T34801300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronx Community District 4 |
E1003223
|
entity |
| Predicate | isInNYCCommunityDistrictSystem |
P43690
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Bronx Community District 4, isInNYCCommunityDistrictSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInNYCCommunityDistrictSystem Context triple: [Bronx Community District 4, isInNYCCommunityDistrictSystem, yes]
-
A.
hasCommunityDistrict
Indicates that an entity is located within, associated with, or falls under the jurisdiction of a specific community district.
-
B.
hasBoroughCommunityDistrictCode
Indicates that a borough is associated with a specific community district code that identifies one of its administrative subdivisions.
-
C.
locatedInBoroughCommunityDistrict
chosen
Indicates that something is situated within a specific borough community district.
-
D.
hasCommunityBoardOfficeBorough
Indicates that a community board’s office is located within a specific borough.
-
E.
isCentralBoroughOf
Indicates that a borough serves as the primary or central administrative or geographic district of a specified city or region.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 3:59 p.m.