Triple
T14088077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 185 |
E339049
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
ME 185
ME 185 is a state highway in Maine that serves as a local connector route, typically linking small communities and other regional roads.
|
E1080374
|
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: ME 185 | Statement: [Maine State Route 185, abbreviation, ME 185]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ME 185 Context triple: [Maine State Route 185, abbreviation, ME 185]
-
A.
ME 183
ME 183 is a short state highway in Maine that serves as a local connector route in Hancock County.
-
B.
ME 181
ME 181 is a state highway in Maine that serves as a regional connector route through Hancock County.
-
C.
ME 184
ME 184 is a state highway in Maine that serves as a local connector route, typically linking small communities and other major roads.
-
D.
ME 167
ME 167 is a state highway in Maine that serves as a regional connector route within the state's road network.
-
E.
ME 160
ME 160 is a state highway in Maine that runs through rural areas of York and Oxford counties, connecting several small towns.
- 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: ME 185 Triple: [Maine State Route 185, abbreviation, ME 185]
Generated description
ME 185 is a state highway in Maine that serves as a local connector route, typically linking small communities and other regional roads.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: ME 185 Target entity description: ME 185 is a state highway in Maine that serves as a local connector route, typically linking small communities and other regional roads.
-
A.
ME 183
ME 183 is a short state highway in Maine that serves as a local connector route in Hancock County.
-
B.
ME 181
ME 181 is a state highway in Maine that serves as a regional connector route through Hancock County.
-
C.
ME 184
ME 184 is a state highway in Maine that serves as a local connector route, typically linking small communities and other major roads.
-
D.
ME 167
ME 167 is a state highway in Maine that serves as a regional connector route within the state's road network.
-
E.
ME 160
ME 160 is a state highway in Maine that runs through rural areas of York and Oxford counties, connecting several small towns.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5ee1ce88819091c983286289337e |
completed | April 14, 2026, 3:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcd0a5c9948190805c2e687c8809ff |
completed | May 7, 2026, 5:49 p.m. |
| NEDg | Description generation | batch_69fcd56da6408190bdbce6581c51d065 |
completed | May 7, 2026, 6:09 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69fcd5f8266081909ff9148a77d63ea8 |
completed | May 7, 2026, 6:12 p.m. |
Created at: April 9, 2026, 10:21 p.m.