Triple
T12812266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Avenue |
E306300
|
entity |
| Predicate | runsThrough |
P416
|
FINISHED |
| Object | Yorkville |
E79563
|
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: [Second Avenue, runsThrough, Yorkville]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yorkville Context triple: [Second Avenue, runsThrough, Yorkville]
-
A.
Yorkville
chosen
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
Yorkville is an upscale Toronto neighborhood known for its luxury shopping, high-end dining, and cultural attractions.
-
C.
Belleville
Belleville is a vibrant, historically working-class neighborhood in northeastern Paris known for its multicultural character, street art, and lively food scene.
-
D.
Belleville
Belleville is a small village in south-central Wisconsin, known for its rural character and proximity to the Madison metropolitan area.
-
E.
Belleville
Belleville is a small Canadian city in southeastern Ontario, known as a regional service and commercial hub on the Bay of Quinte.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e9adcf08190a12801adcc613477 |
completed | April 10, 2026, 9:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f68eca9b448190a819b3807fdbc3f8 |
completed | May 2, 2026, 11:54 p.m. |
Created at: April 9, 2026, 5:31 p.m.