Triple
T20366344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia State Route 338 |
E496918
|
entity |
| Predicate | routeDesignation |
P1864
|
FINISHED |
| Object | SR 338 |
—
|
NE NERFINISHED |
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 338 | Statement: [Georgia State Route 338, routeDesignation, SR 338]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 338 Context triple: [Georgia State Route 338, routeDesignation, SR 338]
-
A.
SR 338
chosen
SR 338 is a Tennessee state highway that serves as a local connector route in the Knoxville metropolitan area.
-
B.
SR 331
SR 331 is a state highway in Ohio that serves as a regional connector route through the eastern part of the state.
-
C.
SR 33
SR 33 is a north–south California state highway that runs from Ventura through the Transverse Ranges and Central Valley, serving both coastal and inland communities.
-
D.
SR 38
SR 38 is a state highway in Georgia that runs east–west across the southern part of the state, connecting several cities and major routes.
-
E.
SR 38
SR 38 is a California state highway that runs through the San Bernardino Mountains, providing scenic access between the Inland Empire and the Big Bear Lake area.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4a4f9b081908a5a021919c21ccb |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67871bfdc8190948c46497cd675c9 |
completed | April 20, 2026, 7:03 p.m. |
Created at: April 16, 2026, 11:26 a.m.