Triple

T10449686
Position Surface form Disambiguated ID Type / Status
Subject Maine State Route 136 E246385 entity
Predicate abbreviation P43 FINISHED
Object 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.
 E863303 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 136 | Statement: [Maine State Route 136, abbreviation, ME 136]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: ME 136
Context triple: [Maine State Route 136, abbreviation, ME 136]
  • 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 132
    ME 132 is a state highway in Maine that serves as a regional connector route between local communities.
  • C. ME 135
    ME 135 is a state highway in Maine that serves as a regional connector route between local communities.
  • D. ME 131
    ME 131 is a state highway in Maine that runs through Knox County, connecting several coastal and inland communities.
  • E. 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.
  • 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 136
Triple: [Maine State Route 136, abbreviation, ME 136]
Generated description
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.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: ME 136
Target entity description: 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.
  • 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 132
    ME 132 is a state highway in Maine that serves as a regional connector route between local communities.
  • C. ME 135
    ME 135 is a state highway in Maine that serves as a regional connector route between local communities.
  • D. ME 131
    ME 131 is a state highway in Maine that runs through Knox County, connecting several coastal and inland communities.
  • E. 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.
  • 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_69d381c04fe08190957c26c526a3b05a completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4fe09af04819083db42f4de4cb0a9 completed April 7, 2026, 12:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69d87efedf6c8190aa4b7bbe5f160eeb completed April 10, 2026, 4:39 a.m.
NEDg Description generation batch_69d886c562c081908aae846da8efb1a5 completed April 10, 2026, 5:12 a.m.
NED2 Entity disambiguation (via description) batch_69d88dce21448190b093b4f548e29f84 completed April 10, 2026, 5:42 a.m.
Created at: April 6, 2026, 12:17 p.m.