Triple
T16664306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nevada State Route 278 |
E404940
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
SR 278
SR 278 is a Nevada state highway that runs generally north–south, connecting the city of Eureka with Interstate 80 near Carlin through rural central Nevada.
|
E1227574
|
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 278 | Statement: [Nevada State Route 278, abbreviation, SR 278]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 278 Context triple: [Nevada State Route 278, abbreviation, SR 278]
-
A.
SR 207
SR 207 is a state highway in Maine that serves as a regional connector route between local communities.
-
B.
SR 208
SR 208 is a short state highway in Maine that connects local communities and provides regional access to larger routes.
-
C.
SR 289
SR 289 is a state highway route, designated with the number 289, that forms part of a regional road network in its jurisdiction.
-
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 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.
- 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 278 Triple: [Nevada State Route 278, abbreviation, SR 278]
Generated description
SR 278 is a Nevada state highway that runs generally north–south, connecting the city of Eureka with Interstate 80 near Carlin through rural central Nevada.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 278 Target entity description: SR 278 is a Nevada state highway that runs generally north–south, connecting the city of Eureka with Interstate 80 near Carlin through rural central Nevada.
-
A.
SR 207
SR 207 is a state highway in Maine that serves as a regional connector route between local communities.
-
B.
SR 208
SR 208 is a short state highway in Maine that connects local communities and provides regional access to larger routes.
-
C.
SR 289
SR 289 is a state highway route, designated with the number 289, that forms part of a regional road network in its jurisdiction.
-
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 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.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37c9be0688190afda306cde934c68 |
completed | April 18, 2026, 12:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a008a32988c8190a671a4cbd829047a |
completed | May 10, 2026, 1:37 p.m. |
| NEDg | Description generation | batch_6a008aed0bfc8190886b6a2e08a885b9 |
completed | May 10, 2026, 1:41 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a008bc0e57c8190838ec383f2a1b52c |
completed | May 10, 2026, 1:44 p.m. |
Created at: April 10, 2026, 5:18 a.m.