Triple
T13454464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia State Route 193 |
E311192
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | SR 193 |
E367117
|
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: SR 193 | Statement: [Virginia State Route 193, hasAbbreviation, SR 193]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 193 Context triple: [Virginia State Route 193, hasAbbreviation, SR 193]
-
A.
SR 193
chosen
SR 193 is a Virginia state highway known as Georgetown Pike, a historic and scenic road in Northern Virginia.
-
B.
SR 190
SR 190 is a California state highway that runs east–west through the southern Sierra Nevada and Death Valley, connecting the Central Valley to the Nevada state line.
-
C.
SR 113
SR 113 is a state highway in northern Ohio that runs east–west through several counties, connecting rural areas with small towns and cities.
-
D.
SR 119
SR 119 is a state highway in Alabama that serves as a regional connector route through several suburban and rural communities.
-
E.
SR 163
SR 163 is a major north–south freeway in San Diego, California, connecting downtown with the inland freeway network and passing through Balboa Park.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaefc52448190b30d7999f44a9765 |
completed | April 12, 2026, 2:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f75d8892a88190b4a32865b32c8883 |
completed | May 3, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:41 p.m.