Triple
T14690471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 23 |
E345020
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Ashland, Kentucky |
E351062
|
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: Ashland, Kentucky | Statement: [U.S. Route 23, passesThrough, Ashland, Kentucky]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ashland, Kentucky Context triple: [U.S. Route 23, passesThrough, Ashland, Kentucky]
-
A.
Ashland, Kentucky
chosen
Ashland, Kentucky is a small industrial and riverfront city in northeastern Kentucky, known as part of the Huntington–Ashland metropolitan area along the Ohio River.
-
B.
Ashland, Ohio
Ashland, Ohio is a small city in north-central Ohio known historically as a regional manufacturing and agricultural center and home to Ashland University.
-
C.
Ashland
Ashland is an unincorporated community in Alameda County, California, situated in the East Bay region of the San Francisco Bay Area.
-
D.
Ashland
Ashland is a Chicago 'L' rapid transit station on the CTA's Pink Line serving the city's Near West Side.
-
E.
Ashland
Ashland is a small borough in Schuylkill County, Pennsylvania, historically known for its anthracite coal mining heritage.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb5844de481908a796eaa474bfde9 |
completed | April 14, 2026, 9:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fde189771c81909289b8b044e32547 |
completed | May 8, 2026, 1:13 p.m. |
Created at: April 10, 2026, 1:28 a.m.