Triple
T10705946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 139 |
E252404
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
ME 139
ME 139 is a state highway in Maine that serves as a regional connector route between several central Maine communities.
|
E880373
|
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 139 | Statement: [Maine State Route 139, abbreviation, ME 139]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ME 139 Context triple: [Maine State Route 139, abbreviation, ME 139]
-
A.
ME 133
ME 133 is a state highway in Maine that serves as a regional connector route between several central Maine communities.
-
B.
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.
-
C.
ME 132
ME 132 is a state highway in Maine that serves as a regional connector route between local communities.
-
D.
ME 135
ME 135 is a state highway in Maine that serves as a regional connector route between local communities.
-
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 139 Triple: [Maine State Route 139, abbreviation, ME 139]
Generated description
ME 139 is a state highway in Maine that serves as a regional connector route between several central Maine communities.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: ME 139 Target entity description: ME 139 is a state highway in Maine that serves as a regional connector route between several central Maine communities.
-
A.
ME 133
ME 133 is a state highway in Maine that serves as a regional connector route between several central Maine communities.
-
B.
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.
-
C.
ME 132
ME 132 is a state highway in Maine that serves as a regional connector route between local communities.
-
D.
ME 135
ME 135 is a state highway in Maine that serves as a regional connector route between local communities.
-
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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fddfbed48190810bb3faee473fde |
completed | April 9, 2026, 1:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d998fe56dc8190ae0c987b28ec6206 |
completed | April 11, 2026, 12:42 a.m. |
| NEDg | Description generation | batch_69d99e8632688190b3746649a124ca09 |
completed | April 11, 2026, 1:06 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69da625a1e8c8190b282e7a70bb7c876 |
completed | April 11, 2026, 3:01 p.m. |
Created at: April 8, 2026, 9:12 p.m.