Triple
T12238336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 160 |
E291660
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
ME 160
ME 160 is a state highway in Maine that runs through rural areas of York and Oxford counties, connecting several small towns.
|
E970901
|
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 160 | Statement: [Maine State Route 160, abbreviation, ME 160]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ME 160 Context triple: [Maine State Route 160, abbreviation, ME 160]
-
A.
ME 136
ME 136 is a state highway in Maine that connects several communities in the southern part of the state and serves as a regional commuter and connector route.
-
B.
ME 114
ME 114 is a state highway in Maine that runs through parts of Cumberland County, connecting several communities and serving as a regional commuter and local access route.
-
C.
ME 139
ME 139 is a state highway in Maine that serves as a regional connector route between several central Maine communities.
-
D.
ME 133
ME 133 is a state highway in Maine that serves as a regional connector route between several central Maine communities.
-
E.
ME 153
ME 153 is a state highway in Maine that serves as a short connector route in the state's road network.
- 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 160 Triple: [Maine State Route 160, abbreviation, ME 160]
Generated description
ME 160 is a state highway in Maine that runs through rural areas of York and Oxford counties, connecting several small towns.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: ME 160 Target entity description: ME 160 is a state highway in Maine that runs through rural areas of York and Oxford counties, connecting several small towns.
-
A.
ME 136
ME 136 is a state highway in Maine that connects several communities in the southern part of the state and serves as a regional commuter and connector route.
-
B.
ME 114
ME 114 is a state highway in Maine that runs through parts of Cumberland County, connecting several communities and serving as a regional commuter and local access route.
-
C.
ME 139
ME 139 is a state highway in Maine that serves as a regional connector route between several central Maine communities.
-
D.
ME 133
ME 133 is a state highway in Maine that serves as a regional connector route between several central Maine communities.
-
E.
ME 153
ME 153 is a state highway in Maine that serves as a short connector route in the state's road network.
- 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_69d6ab668acc8190963ba424049d6aee |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91cb45340819093365f8efdf85f75 |
completed | April 10, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f60ab3ae2481908f65d8ac61a6b2e4 |
completed | May 2, 2026, 2:31 p.m. |
| NEDg | Description generation | batch_69f60bdd8d508190813178ff4c77afcf |
completed | May 2, 2026, 2:36 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f60c67c680819087630d190d0a008f |
completed | May 2, 2026, 2:38 p.m. |
Created at: April 8, 2026, 9:51 p.m.