Triple
T11421520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 148 |
E270632
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
SR 148
SR 148 is a state highway in Maine that serves as a regional connector route through rural communities.
|
E924523
|
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 148 | Statement: [Maine State Route 148, abbreviation, SR 148]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 148 Context triple: [Maine State Route 148, abbreviation, SR 148]
-
A.
SR 14
SR 14 is a state highway in Georgia that serves as a key transportation route connecting several communities in the western part of the state.
-
B.
SR 14
SR 14 is a major north–south California state highway connecting Los Angeles to the high desert and serving as a key route through the Antelope Valley.
-
C.
SR 14
SR 14 is a state highway in Washington that runs along the Columbia River in the southern part of the state, serving as an important east–west transportation corridor.
-
D.
SR 143
SR 143 is a short Arizona state highway in the Phoenix metropolitan area that primarily serves as a connector between Interstate 10 and Phoenix Sky Harbor International Airport.
-
E.
SR 143
SR 143 is a state highway in Maine that serves as a regional connector route between local communities.
- 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 148 Triple: [Maine State Route 148, abbreviation, SR 148]
Generated description
SR 148 is a state highway in Maine that serves as a regional connector route through rural communities.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 148 Target entity description: SR 148 is a state highway in Maine that serves as a regional connector route through rural communities.
-
A.
SR 14
SR 14 is a state highway in Georgia that serves as a key transportation route connecting several communities in the western part of the state.
-
B.
SR 14
SR 14 is a state highway in Washington that runs along the Columbia River in the southern part of the state, serving as an important east–west transportation corridor.
-
C.
SR 14
SR 14 is a major north–south California state highway connecting Los Angeles to the high desert and serving as a key route through the Antelope Valley.
-
D.
SR 143
SR 143 is a short Arizona state highway in the Phoenix metropolitan area that primarily serves as a connector between Interstate 10 and Phoenix Sky Harbor International Airport.
-
E.
SR 143
SR 143 is a state highway in Maine that serves as a regional connector route between local communities.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d801b357e88190ace56d36a945688f |
completed | April 9, 2026, 7:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5b88f80d88190b91b63d0b7457c25 |
completed | April 20, 2026, 5:24 a.m. |
| NEDg | Description generation | batch_69e5c28d3824819097ff84cb4e13c923 |
completed | April 20, 2026, 6:07 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69e5c451c6c88190bcbb1f54ede35d29 |
completed | April 20, 2026, 6:14 a.m. |
Created at: April 8, 2026, 9:34 p.m.