Triple
T16824140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California State Route 29 |
E408971
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 29 |
E553795
|
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 29 | Statement: [California State Route 29, abbreviation, SR 29]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 29 Context triple: [California State Route 29, abbreviation, SR 29]
-
A.
SR 29
chosen
SR 29 is a California state highway that runs through Napa Valley, serving as a major route to the region’s renowned wine country.
-
B.
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.
-
C.
SR 28
SR 28 is a state highway in Washington that runs through central and eastern parts of the state, connecting communities along the Columbia River.
-
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 209
SR 209 is a state highway in Maine that serves as a primary route connecting inland areas to the coastal town of Phippsburg and nearby shoreline communities.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b310ffec81908087e5aaacc4a7c2 |
completed | April 18, 2026, 4:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00d452505c8190b6d37b54b2f665f0 |
completed | May 10, 2026, 6:54 p.m. |
Created at: April 10, 2026, 5:23 a.m.