Triple
T29111148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East 241st Street |
E736907
|
entity |
| Predicate | neighborhoodEdgeOf |
P16140
|
FINISHED |
| Object | Wakefield, Bronx |
—
|
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: Wakefield, Bronx | Statement: [East 241st Street, neighborhoodEdgeOf, Wakefield, Bronx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighborhoodEdgeOf Context triple: [East 241st Street, neighborhoodEdgeOf, Wakefield, Bronx]
-
A.
hasNeighborhoodAlong
chosen
Indicates that one entity has a neighboring area or region that extends along the boundary or length of another entity.
-
B.
partOfNeighborhoodNetwork
Indicates that an entity belongs to, or is included within, a specific neighborhood’s interconnected network or system.
-
C.
neighborhood
Indicates that one entity is located in close spatial proximity to another, typically within the same local area or district.
-
D.
hasNearbyStreet
Indicates that one entity is located close to or adjacent to a street.
-
E.
hasNeighbourhood
Indicates that one entity is located within, or is associated with, a particular neighborhood area of 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 28, 2026, 11:18 a.m.