Triple
T37829697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Tremont Avenue |
E943164
|
entity |
| Predicate | hasBoroughCommunity |
P197503
|
FINISHED |
| Object | East Tremont |
—
|
NE NERFINISHED |
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: East Tremont | Statement: [East Tremont Avenue, hasBoroughCommunity, East Tremont]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoroughCommunity Context triple: [East Tremont Avenue, hasBoroughCommunity, East Tremont]
-
A.
hasBorough
Indicates that one entity is located within, belongs to, or is administratively part of a specific borough.
-
B.
hasBoroughOrNeighborhood
Indicates that a place is located within, or associated with, a specific borough or neighborhood.
-
C.
hasBoroughCommunityDistrictCode
Indicates that a borough is associated with a specific community district code that identifies one of its administrative subdivisions.
-
D.
hasBoroughEndpoint
Indicates that something has an endpoint located within a specific borough.
-
E.
hasBoroughSegment
Indicates that something is a specific segment or portion within a larger 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
| PDg | Predicate description generation | batch_69fe96c0b760819093737292d33df165 |
completed | May 9, 2026, 2:06 a.m. |
Created at: May 3, 2026, 4:19 p.m.