Triple
T24113130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Staten Island Community District 3 |
E597432
|
entity |
| Predicate | hasBoroughCommunityDistrictCode |
P155105
|
FINISHED |
| Object | 503 |
—
|
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: 503 | Statement: [Staten Island Community District 3, hasBoroughCommunityDistrictCode, 503]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoroughCommunityDistrictCode Context triple: [Staten Island Community District 3, hasBoroughCommunityDistrictCode, 503]
-
A.
hasBoroughCode
Indicates that an entity is associated with a specific borough identified by a particular code.
-
B.
locatedInBoroughCommunityDistrict
Indicates that something is situated within a specific borough community district.
-
C.
hasBorough
Indicates that one entity is located within, belongs to, or is administratively part of a specific borough.
-
D.
hasBoroughOrNeighborhood
Indicates that a place is located within, or associated with, a specific borough or neighborhood.
-
E.
hasBoroughEndpoint
Indicates that something has an endpoint located within a specific borough.
- F. None of above. chosen
Provenance (4 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_69e288c74200819098ab875b592cb39f |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1de1cf75c8190ad5352d4b290e735 |
completed | April 29, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17b58012c81909106b332db399023 |
completed | April 29, 2026, 3:30 a.m. |
Created at: April 17, 2026, 11:03 p.m.