Triple
T8534482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Route 397 |
E202042
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
SR 397
SR 397 is a state highway designated as State Route 397, typically serving as a regional connector within a U.S. state's road network.
|
E743172
|
NE FINISHED |
How this triple was built (4 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 397 | Statement: [State Route 397, abbreviation, SR 397]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 397 Context triple: [State Route 397, abbreviation, SR 397]
-
A.
SR 374
SR 374 is a Nevada state highway that provides access to Death Valley National Park from the town of Beatty.
-
B.
SR 36
SR 36 is a scenic east–west state highway in Northern California that traverses rural mountains and forests, connecting the North Coast near Fortuna to the northern Central Valley near Red Bluff.
-
C.
SR 316
SR 316 is a major east–west state highway in Georgia that connects the Atlanta metropolitan area with the city of Athens.
-
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 32
SR 32 is a major east–west state highway in Ohio that spans much of the southern part of the state, connecting Cincinnati to the Ohio River valley and Appalachian regions.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: SR 397 Triple: [State Route 397, abbreviation, SR 397]
Generated description
SR 397 is a state highway designated as State Route 397, typically serving as a regional connector within a U.S. state's road network.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 397 Target entity description: SR 397 is a state highway designated as State Route 397, typically serving as a regional connector within a U.S. state's road network.
-
A.
SR 374
SR 374 is a Nevada state highway that provides access to Death Valley National Park from the town of Beatty.
-
B.
SR 36
SR 36 is a scenic east–west state highway in Northern California that traverses rural mountains and forests, connecting the North Coast near Fortuna to the northern Central Valley near Red Bluff.
-
C.
SR 316
SR 316 is a major east–west state highway in Georgia that connects the Atlanta metropolitan area with the city of Athens.
-
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 32
SR 32 is a major east–west state highway in Ohio that spans much of the southern part of the state, connecting Cincinnati to the Ohio River valley and Appalachian regions.
- F. None of above. chosen
Provenance (5 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_69ca832355b08190b8b6a4ab4a4a3554 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6a0ccd4819097b41d0dfb1c5018 |
completed | March 31, 2026, 3:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce890eb0b48190aa76cc955d00ec18 |
completed | April 2, 2026, 3:19 p.m. |
| NEDg | Description generation | batch_69ce8a9ba0448190ae7637f24b8a8032 |
completed | April 2, 2026, 3:26 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ce8bda33548190a8f6985a48d65a39 |
completed | April 2, 2026, 3:31 p.m. |
Created at: March 30, 2026, 6:17 p.m.