Triple
T12444575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky Route 224 |
E297363
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
KY 224
KY 224 is a state highway in Kentucky that serves as a regional connector route through several rural communities.
|
E985067
|
NE FINISHED |
How this triple was built (4 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: KY 224 | Statement: [Kentucky Route 224, abbreviation, KY 224]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KY 224 Context triple: [Kentucky Route 224, abbreviation, KY 224]
-
A.
KY 210
KY 210 is a state highway in Kentucky that connects the city of Elizabethtown with the Campbellsville area, serving as a regional route through central Kentucky.
-
B.
KY 218
KY 218 is a state highway in Kentucky that serves as a regional connector route through several rural communities.
-
C.
KY 84
KY 84 is a state highway in Kentucky that serves as a regional connector route through several central Kentucky counties.
-
D.
KY 313
KY 313 is a state highway in Kentucky that serves as a regional connector route, primarily in the central part of the state.
-
E.
KY 33
KY 33 is a state highway in Kentucky that connects the city of Danville with the Lexington area, passing through central Bluegrass region communities.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: KY 224 Triple: [Kentucky Route 224, abbreviation, KY 224]
Generated description
KY 224 is a state highway in Kentucky that serves as a regional connector route through several rural communities.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: KY 224 Target entity description: KY 224 is a state highway in Kentucky that serves as a regional connector route through several rural communities.
-
A.
KY 210
KY 210 is a state highway in Kentucky that connects the city of Elizabethtown with the Campbellsville area, serving as a regional route through central Kentucky.
-
B.
KY 218
KY 218 is a state highway in Kentucky that serves as a regional connector route through several rural communities.
-
C.
KY 84
KY 84 is a state highway in Kentucky that serves as a regional connector route through several central Kentucky counties.
-
D.
KY 313
KY 313 is a state highway in Kentucky that serves as a regional connector route, primarily in the central part of the state.
-
E.
KY 33
KY 33 is a state highway in Kentucky that connects the city of Danville with the Lexington area, passing through central Bluegrass region communities.
- F. None of above. chosen
Provenance (5 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_69d6ada166c48190b902972cd2408fa3 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94d8fd9848190a83410353d88ea8d |
completed | April 10, 2026, 7:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f63f132d048190b58a8381bdc74cad |
completed | May 2, 2026, 6:14 p.m. |
| NEDg | Description generation | batch_69f6415f11d88190a9f77eb1890f76ef |
completed | May 2, 2026, 6:24 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f64231606481909b8dd9d878670a6c |
completed | May 2, 2026, 6:28 p.m. |
Created at: April 8, 2026, 9:55 p.m.