Triple
T16339855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 93 Alternate |
E396767
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | US 93 Alt |
E396767
|
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: US 93 Alt | Statement: [U.S. Route 93 Alternate, hasAbbreviation, US 93 Alt]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: US 93 Alt Context triple: [U.S. Route 93 Alternate, hasAbbreviation, US 93 Alt]
-
A.
U.S. Route 93 Alternate
chosen
U.S. Route 93 Alternate is an alternate alignment of U.S. Route 93 in northeastern Nevada that provides an additional north–south highway corridor through Elko County.
-
B.
U.S. Route 95A
U.S. Route 95A is an alternate U.S. highway in western Nevada that branches from U.S. Route 95 to serve communities such as Fernley and Yerington.
-
C.
SR 95
SR 95 is a north–south Arizona state highway that runs largely along the Colorado River, serving communities and recreational areas in western Arizona.
-
D.
SR 97
SR 97 is a state highway in Georgia that serves as a regional connector route through the southwestern part of the state.
-
E.
SR 91
SR 91 is a state highway designation used for specific numbered routes within a U.S. state's road network.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2da08fbc88190a31127d10ca633d6 |
completed | April 18, 2026, 1:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a002dadcaa48190865cec201cde47e3 |
completed | May 10, 2026, 7:03 a.m. |
Created at: April 10, 2026, 5:07 a.m.