Triple
T34801319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronx CD4 |
E1003224
|
entity |
| Predicate | boroughCommunityDistrictCode |
P13282
|
FINISHED |
| Object | 204 |
—
|
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: 204 | Statement: [Bronx CD4, boroughCommunityDistrictCode, 204]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boroughCommunityDistrictCode Context triple: [Bronx CD4, boroughCommunityDistrictCode, 204]
-
A.
localAuthorityDistrictCode
Indicates the specific local authority district to which an entity is administratively assigned, represented by its official code.
-
B.
communityDistrictNumber
chosen
Indicates the specific community district identifier associated with an entity or location.
-
C.
boroughOrCommunityArea
Indicates that one place is a borough or community area subdivision within the jurisdiction or boundaries of another place.
-
D.
communityServicesDistrictFormationYear
Indicates the year in which a community services district was officially formed or established.
-
E.
formerLocalAuthorityArea
Indicates that one entity was previously a local authority administrative area that is associated with, or has been succeeded by, another entity.
- 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_69f77a89c4e88190a048e95d42b4a084 |
completed | May 3, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_69f7795b1abc8190823664d1caa94649 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.