Triple

T12729536
Position Surface form Disambiguated ID Type / Status
Subject Maine State Route 167 E304195 entity
Predicate hasAbbreviation P43 FINISHED
Object ME 167
ME 167 is a state highway in Maine that serves as a regional connector route within the state's road network.
 E1001096 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 167 | Statement: [Maine State Route 167, hasAbbreviation, ME 167]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: ME 167
Context triple: [Maine State Route 167, hasAbbreviation, ME 167]
  • A. ME 164
    ME 164 is a state highway in northern Maine that connects the communities of Presque Isle and Caribou in Aroostook County.
  • B. ME 160
    ME 160 is a state highway in Maine that runs through rural areas of York and Oxford counties, connecting several small towns.
  • C. 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.
  • D. 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.
  • 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 167
Triple: [Maine State Route 167, hasAbbreviation, ME 167]
Generated description
ME 167 is a state highway in Maine that serves as a regional connector route within the state's road network.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: ME 167
Target entity description: ME 167 is a state highway in Maine that serves as a regional connector route within the state's road network.
  • A. ME 164
    ME 164 is a state highway in northern Maine that connects the communities of Presque Isle and Caribou in Aroostook County.
  • B. ME 160
    ME 160 is a state highway in Maine that runs through rural areas of York and Oxford counties, connecting several small towns.
  • C. 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.
  • D. 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.
  • 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_69d7bdf1426c8190a4402e1c4cdec33a completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d964172490819080cd022ff8290b6e completed April 10, 2026, 8:56 p.m.
NED1 Entity disambiguation (via context triple) batch_69f67c8a4b7c8190a514b623a7364fd7 completed May 2, 2026, 10:36 p.m.
NEDg Description generation batch_69f67d663fd08190a00b30a7ff260c70 completed May 2, 2026, 10:40 p.m.
NED2 Entity disambiguation (via description) batch_69f67e0f48e4819085905564f5540f37 completed May 2, 2026, 10:43 p.m.
Created at: April 9, 2026, 5:25 p.m.