Triple
T14429119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 25 |
E357774
|
entity |
| Predicate | connectsCity |
P4245
|
FINISHED |
| Object | London, Kentucky |
E364086
|
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: London, Kentucky | Statement: [U.S. Route 25, connectsCity, London, Kentucky]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: London, Kentucky Context triple: [U.S. Route 25, connectsCity, London, Kentucky]
-
A.
London, Kentucky
chosen
London, Kentucky is a small city in southeastern Kentucky that serves as a regional hub for government, commerce, and transportation.
-
B.
Melbourne, Kentucky
Melbourne, Kentucky is a small city in northern Kentucky situated along the Ohio River within the Cincinnati metropolitan area.
-
C.
Lancaster, Kentucky
Lancaster, Kentucky is a small historic city in central Kentucky that serves as the county seat of Garrard County.
-
D.
Kingston, Kentucky
Kingston, Kentucky is a small unincorporated community in Madison County that lies between Richmond and Berea in central Kentucky.
-
E.
Manchester, Kentucky
Manchester, Kentucky is a small city in Clay County that serves as a regional hub for education, healthcare, and commerce in southeastern Kentucky.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91154de881909266ae88d1545685 |
completed | April 14, 2026, 7:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd94a254f881908d9494d4602064ae |
completed | May 8, 2026, 7:45 a.m. |
Created at: April 10, 2026, 1:18 a.m.