Triple

T12977740
Position Surface form Disambiguated ID Type / Status
Subject Maine State Route 176 E321572 entity
Predicate abbreviation P43 FINISHED
Object ME 176
ME 176 is a state highway in Maine that serves as a local connector route through Hancock County’s coastal communities.
 E1012487 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 176 | Statement: [Maine State Route 176, abbreviation, ME 176]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: ME 176
Context triple: [Maine State Route 176, abbreviation, ME 176]
  • A. ME 167
    ME 167 is a state highway in Maine that serves as a regional connector route within the state's road network.
  • 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 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.
  • D. ME 148
    ME 148 is a state highway in Maine that serves as a regional connector route between local communities.
  • E. ME 168
    ME 168 is a state highway in Maine that serves as a short connector route between local communities in the region.
  • 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 176
Triple: [Maine State Route 176, abbreviation, ME 176]
Generated description
ME 176 is a state highway in Maine that serves as a local connector route through Hancock County’s coastal communities.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: ME 176
Target entity description: ME 176 is a state highway in Maine that serves as a local connector route through Hancock County’s coastal communities.
  • A. ME 167
    ME 167 is a state highway in Maine that serves as a regional connector route within the state's road network.
  • 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 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.
  • D. ME 148
    ME 148 is a state highway in Maine that serves as a regional connector route between local communities.
  • E. ME 168
    ME 168 is a state highway in Maine that serves as a short connector route between local communities in the region.
  • 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_69d80763bd6c819094437da5b20b01d2 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d97e59a4c88190907d05b8d57dae89 completed April 10, 2026, 10:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6b8f0315c8190aae5908ba65d5867 completed May 3, 2026, 2:54 a.m.
NEDg Description generation batch_69f6b9dc31ec819093c89ff0a1ccbfa1 completed May 3, 2026, 2:58 a.m.
NED2 Entity disambiguation (via description) batch_69f6baacd7548190af5514923a0dee26 completed May 3, 2026, 3:02 a.m.
Created at: April 9, 2026, 8:38 p.m.