Triple

T9815966
Position Surface form Disambiguated ID Type / Status
Subject Maine State Route 132 E238404 entity
Predicate abbreviation P43 FINISHED
Object ME 132
ME 132 is a state highway in Maine that serves as a regional connector route between local communities.
E823386 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 132 | Statement: [Maine State Route 132, abbreviation, ME 132]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ME 132
Context triple: [Maine State Route 132, abbreviation, ME 132]
  • A. ME 131
    ME 131 is a state highway in Maine that runs through Knox County, connecting several coastal and inland communities.
  • B. 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.
  • C. ME 152
    ME 152 is a state highway in Maine that serves as a regional connector route between local communities.
  • D. ME 122
    ME 122 is a state highway in Maine that serves as a short connector route between local communities and major regional roads.
  • E. 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.
  • 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 132
Triple: [Maine State Route 132, abbreviation, ME 132]
Generated description
ME 132 is a state highway in Maine that serves as a regional connector route between local communities.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: ME 132
Target entity description: ME 132 is a state highway in Maine that serves as a regional connector route between local communities.
  • A. ME 131
    ME 131 is a state highway in Maine that runs through Knox County, connecting several coastal and inland communities.
  • B. 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.
  • C. ME 152
    ME 152 is a state highway in Maine that serves as a regional connector route between local communities.
  • D. ME 122
    ME 122 is a state highway in Maine that serves as a short connector route between local communities and major regional roads.
  • E. 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.
  • 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_69ca84dfde1481909f47c286d715f892 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb2f341648190bf8343e1124085cb completed April 2, 2026, 12:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1cc6c64dc8190979be34255dc22e5 completed April 5, 2026, 2:43 a.m.
NEDg Description generation batch_69d1cf7ce46c8190a7383086eb667b51 completed April 5, 2026, 2:57 a.m.
NED2 Entity disambiguation (via description) batch_69d1d0034dc081908182e3f873a2c584 completed April 5, 2026, 2:59 a.m.
Created at: March 30, 2026, 8:30 p.m.