Triple
T9320330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Route 24 |
E224235
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 24 |
E708206
|
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 24 | Statement: [State Route 24, abbreviation, SR 24]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 24 Context triple: [State Route 24, abbreviation, SR 24]
-
A.
SR 24
chosen
SR 24 is a Florida state highway that runs east–west, connecting the Gulf Coast near Cedar Key to Gainesville and other inland communities.
-
B.
SR 243
SR 243 is a short primary state highway in Fairfax County, Virginia, serving as a connector route in the suburban Washington, D.C. metropolitan area.
-
C.
SR 28
SR 28 is a scenic Nevada state highway that runs along the northeastern shore of Lake Tahoe, connecting U.S. Route 50 near Spooner Lake to the California state line.
-
D.
SR 28
SR 28 is a primary state highway in Virginia that serves as a major north–south transportation corridor in the northern part of the state.
-
E.
SR 29
SR 29 is a California state highway that runs through Napa Valley, serving as a major route to the region’s renowned wine country.
- 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_69ca8426d48481909596360f7791c7dd |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd358dcb4c81909e00bfb58a6dda3f |
completed | April 1, 2026, 3:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0c7cc71e48190afdc3f1120ce5e02 |
completed | April 4, 2026, 8:11 a.m. |
Created at: March 30, 2026, 7:38 p.m.