Triple
T10057911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 114 |
E208908
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
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.
|
E838703
|
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 114 | Statement: [Maine State Route 114, abbreviation, ME 114]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ME 114 Context triple: [Maine State Route 114, abbreviation, ME 114]
-
A.
ME 115
ME 115 is a state highway in Maine that serves as a regional connector route between several communities in the southern part of the state.
-
B.
ME 111
ME 111 is a state highway in Maine that serves as a key east–west route connecting several communities in the southern part of the state.
-
C.
ME 112
ME 112 is a state highway in Maine that serves as a regional connector route between several communities in the southern part of the state.
-
D.
ME 121
ME 121 is a state highway in Maine that serves as a regional connector route through several communities in the western part of the state.
-
E.
ME 131
ME 131 is a state highway in Maine that runs through Knox County, connecting several coastal and inland 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 114 Triple: [Maine State Route 114, abbreviation, ME 114]
Generated description
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.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: ME 114 Target entity description: 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.
-
A.
ME 115
ME 115 is a state highway in Maine that serves as a regional connector route between several communities in the southern part of the state.
-
B.
ME 111
ME 111 is a state highway in Maine that serves as a key east–west route connecting several communities in the southern part of the state.
-
C.
ME 112
ME 112 is a state highway in Maine that serves as a regional connector route between several communities in the southern part of the state.
-
D.
ME 121
ME 121 is a state highway in Maine that serves as a regional connector route through several communities in the western part of the state.
-
E.
ME 131
ME 131 is a state highway in Maine that runs through Knox County, connecting several coastal and inland 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_69ca836094408190a36a1ea7e9a86fcd |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcfaf7700819084dedf7b63e789c1 |
completed | April 2, 2026, 2:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d29a5d4b308190b5b1ece1ca99be86 |
completed | April 5, 2026, 5:22 p.m. |
| NEDg | Description generation | batch_69d29b7430248190b8965eaf1286dd7c |
completed | April 5, 2026, 5:27 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d29c7ba9f081908f4614098d6c954b |
completed | April 5, 2026, 5:31 p.m. |
Created at: March 30, 2026, 8:57 p.m.