Triple
T2356171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bloor–Yonge station |
E47560
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Yorkville |
E49088
|
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: Yorkville | Statement: [Bloor–Yonge station, locatedIn, Yorkville]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yorkville Context triple: [Bloor–Yonge station, locatedIn, Yorkville]
-
A.
Yorkville
Yorkville is a residential neighborhood on Manhattan’s Upper East Side known for its historic German and Central European roots and its mix of tenements, brownstones, and modern high-rises.
-
B.
Yorkville
chosen
Yorkville is an upscale Toronto neighborhood known for its luxury shopping, high-end dining, and cultural attractions.
-
C.
Garden City
Garden City is the nickname of Missoula, Montana, reflecting its lush, green landscape and abundant trees.
-
D.
Garden City
Garden City is the popular nickname of Port Harcourt, a major oil-producing city in southern Nigeria known for its greenery and urban parks.
-
E.
Garden City
Garden City is a popular nickname for Bengaluru, highlighting its historic abundance of parks, trees, and green spaces.
- 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_69a88a1b678c8190bce986922ba60ce0 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc6fd4e488190b763a1c9b5d18f2c |
completed | March 7, 2026, 6:34 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae963660108190b58f3288a5b3f96e |
completed | March 9, 2026, 9:43 a.m. |
Created at: March 4, 2026, 7:54 p.m.