Triple
T10713291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Englewood |
E252595
|
entity |
| Predicate | hasMajorStreet |
P30026
|
FINISHED |
| Object | 63rd Street |
E234306
|
NE 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: 63rd Street | Statement: [Englewood, hasMajorStreet, 63rd Street]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 63rd Street Context triple: [Englewood, hasMajorStreet, 63rd Street]
-
A.
63rd Street
chosen
63rd Street is a major east–west thoroughfare on the South Side of Chicago that runs through several neighborhoods and provides access to parks and lakefront areas.
-
B.
86th Street
86th Street is a New York City Subway station on Manhattan’s Upper West Side, serving the IRT Broadway–Seventh Avenue Line.
-
C.
86th Street
86th Street is a major local subway station on Manhattan’s Upper East Side serving the Lexington Avenue Line.
-
D.
57th Street
57th Street is a major east–west thoroughfare in Midtown Manhattan known for its luxury shopping, high-end residences, and prominent commercial buildings.
-
E.
157th Street
157th Street is a New York City Subway station in Manhattan on the IRT Broadway–Seventh Avenue Line.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fe54465081909640f6d7a2314fcb |
completed | April 9, 2026, 1:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de554ed3848190bba56ab52c05902c |
completed | April 14, 2026, 2:55 p.m. |
Created at: April 8, 2026, 9:13 p.m.