Triple
T8705920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronx Community District 12 |
E206649
|
entity |
| Predicate | locationWithinBorough |
P43690
|
FINISHED |
| Object | north-central Bronx |
—
|
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: north-central Bronx | Statement: [Bronx Community District 12, locationWithinBorough, north-central Bronx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationWithinBorough Context triple: [Bronx Community District 12, locationWithinBorough, north-central Bronx]
-
A.
locatedInBoroughCommunityDistrict
chosen
Indicates that something is situated within a specific borough community district.
-
B.
hasBoroughEndpoint
Indicates that something has an endpoint located within a specific borough.
-
C.
hasBorough
Indicates that one entity is located within, belongs to, or is administratively part of a specific borough.
-
D.
hasNearbyBorough
Indicates that one borough is geographically close to or adjacent to another borough.
-
E.
containsEntireBorough
Indicates that one entity fully encompasses the whole geographic area of a borough within its boundaries.
- 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_69ca835645e881908f00e3c8b51da81d |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc58fcac748190a82b57aeb7c43df9 |
completed | March 31, 2026, 11:30 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.