Triple
T14219400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 191 |
E352446
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
ME 191
ME 191 is a state highway in Maine that runs through Washington County, connecting several coastal and inland communities.
|
E1087789
|
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 191 | Statement: [Maine State Route 191, abbreviation, ME 191]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ME 191 Context triple: [Maine State Route 191, abbreviation, ME 191]
-
A.
ME 190
ME 190 is a state highway in Maine that serves as a short connector route in the eastern part of the state.
-
B.
ME 171
ME 171 is a state highway in Maine that serves as a local connector route within the state's road network.
-
C.
ME 178
ME 178 is a state highway in Maine that serves as a regional connector route between communities in the eastern part of the state.
-
D.
ME 181
ME 181 is a state highway in Maine that serves as a regional connector route through Hancock County.
-
E.
ME 176
ME 176 is a state highway in Maine that serves as a local connector route through Hancock County’s coastal 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: ME 191 Triple: [Maine State Route 191, abbreviation, ME 191]
Generated description
ME 191 is a state highway in Maine that runs through Washington County, connecting several coastal and inland communities.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: ME 191 Target entity description: ME 191 is a state highway in Maine that runs through Washington County, connecting several coastal and inland communities.
-
A.
ME 190
ME 190 is a state highway in Maine that serves as a short connector route in the eastern part of the state.
-
B.
ME 171
ME 171 is a state highway in Maine that serves as a local connector route within the state's road network.
-
C.
ME 178
ME 178 is a state highway in Maine that serves as a regional connector route between communities in the eastern part of the state.
-
D.
ME 181
ME 181 is a state highway in Maine that serves as a regional connector route through Hancock County.
-
E.
ME 176
ME 176 is a state highway in Maine that serves as a local connector route through Hancock County’s coastal 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_69d8278a06e481908b5d6af0a8afe737 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de621258d4819085f358cd2cf109e4 |
completed | April 14, 2026, 3:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd28121a288190975d5852f9a503d4 |
completed | May 8, 2026, 12:02 a.m. |
| NEDg | Description generation | batch_69fd29d254608190a9f0b8e5623451aa |
completed | May 8, 2026, 12:09 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69fd2aa5bf3c8190bb62ce780d417b7d |
completed | May 8, 2026, 12:13 a.m. |
Created at: April 10, 2026, 1:06 a.m.