Triple

T12547248
Position Surface form Disambiguated ID Type / Status
Subject Maine State Route 165 E300002 entity
Predicate connectsTo P845 FINISHED
Object Maine State Route 212 E393872 NE FINISHED

How this triple was built (2 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: Maine State Route 212 | Statement: [Maine State Route 165, connectsTo, Maine State Route 212]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maine State Route 212
Context triple: [Maine State Route 165, connectsTo, Maine State Route 212]
  • A. Maine State Route 212 chosen
    Maine State Route 212 is a state highway in Maine that serves as a regional connector between small communities in the northern part of the state.
  • B. Maine State Route 216
    Maine State Route 216 is a state highway in Maine that serves as a local connector route within the state’s numbered highway network.
  • C. Maine State Route 213
    Maine State Route 213 is a state highway in Maine that serves as a regional connector road within the state's numbered route network.
  • D. Maine State Route 210
    Maine State Route 210 is a former state highway in Maine that once served as a short connector route within the state’s numbered highway system.
  • E. Maine State Route 217
    Maine State Route 217 is a short state highway in Maine that serves as a local connector route within the state’s numbered highway network.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d6ada707008190aaec1238117c9379 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d95481ba28819099f7cd2de02e8837 completed April 10, 2026, 7:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69f65eb317148190990d47f50324a1b1 completed May 2, 2026, 8:29 p.m.
Created at: April 8, 2026, 9:57 p.m.