Triple
T10357404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 135 |
E244033
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
SR 135
SR 135 is a state highway in Maine that serves as a regional connector route between local communities.
|
E861424
|
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 135 | Statement: [Maine State Route 135, abbreviation, SR 135]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 135 Context triple: [Maine State Route 135, abbreviation, SR 135]
-
A.
SR 131
SR 131 is a state highway in Maine that runs through Knox and Waldo counties, connecting several coastal and inland communities.
-
B.
SR 132
SR 132 is a state highway in Maine that connects several small communities and links with other major regional routes.
-
C.
SR 133
SR 133 is a state highway in Maine that connects several central Maine communities and serves as a regional north–south transportation route.
-
D.
SR 138
SR 138 is a state highway in Georgia that runs east–west through several counties in the Atlanta metropolitan area, serving as a key regional connector.
-
E.
SR 113
SR 113 is a state highway in northern Ohio that runs east–west through several counties, connecting rural areas with small towns and cities.
- 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 135 Triple: [Maine State Route 135, abbreviation, SR 135]
Generated description
SR 135 is a state highway in Maine that serves as a regional connector route between local communities.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 135 Target entity description: SR 135 is a state highway in Maine that serves as a regional connector route between local communities.
-
A.
SR 131
SR 131 is a state highway in Maine that runs through Knox and Waldo counties, connecting several coastal and inland communities.
-
B.
SR 132
SR 132 is a state highway in Maine that connects several small communities and links with other major regional routes.
-
C.
SR 133
SR 133 is a state highway in Maine that connects several central Maine communities and serves as a regional north–south transportation route.
-
D.
SR 138
SR 138 is a state highway in Georgia that runs east–west through several counties in the Atlanta metropolitan area, serving as a key regional connector.
-
E.
SR 113
SR 113 is a state highway in northern Ohio that runs east–west through several counties, connecting rural areas with small towns and cities.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9563ea48190b8702b3ef497ed9a |
completed | April 7, 2026, 11:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d7fb827cd4819094bead4304795c33 |
completed | April 9, 2026, 7:18 p.m. |
| NEDg | Description generation | batch_69d822d303888190aa556287b3b1cc03 |
completed | April 9, 2026, 10:06 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d859b05a3881908c97cb173d160e44 |
completed | April 10, 2026, 2 a.m. |
Created at: April 6, 2026, 11:58 a.m.