Triple
T16724077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee State Route 92 |
E406422
|
entity |
| Predicate | hasRouteDesignation |
P5539
|
FINISHED |
| Object | SR 92 |
E819490
|
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 92 | Statement: [Tennessee State Route 92, hasRouteDesignation, SR 92]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 92 Context triple: [Tennessee State Route 92, hasRouteDesignation, SR 92]
-
A.
SR 92
chosen
SR 92 is a major east–west state highway in California that includes the San Mateo–Hayward Bridge across San Francisco Bay, connecting the Peninsula with the East Bay.
-
B.
SR 91
SR 91 is a state highway designation used for specific numbered routes within a U.S. state's road network.
-
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 9
SR 9 is a north–south state highway in Washington that runs through Snohomish and Skagit counties, serving as a parallel alternative to Interstate 5.
-
E.
SR 9
SR 9 is a primary state highway in Virginia that runs through the northern part of the state, connecting rural communities to the Washington, D.C. metropolitan area.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e38745d2048190b476e5aa83ec7fec |
completed | April 18, 2026, 1:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00aaef72fc8190975edfe5076ed9db |
completed | May 10, 2026, 3:57 p.m. |
Created at: April 10, 2026, 5:20 a.m.