Triple

T4426684
Position Surface form Disambiguated ID Type / Status
Subject Massachusetts Route 85 E95225 entity
Predicate serves P98 FINISHED
Object Milford central business district E250058 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: Milford central business district | Statement: [Massachusetts Route 85, serves, Milford central business district]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Milford central business district
Context triple: [Massachusetts Route 85, serves, Milford central business district]
  • A. Milford
    Milford is a coastal city in southern Connecticut known for its beaches and harbors along Long Island Sound.
  • B. Milford
    Milford is a village in Surrey, England, situated near the town of Godalming.
  • C. Milford chosen
    Milford is a town in central Massachusetts known for its historic granite quarries and suburban residential character.
  • D. Milford
    Milford is a New Hampshire town in Hillsborough County known historically for its mill industry and its location along the Souhegan River.
  • E. Milford
    Milford is a locality associated with the city of Salisbury, likely recognized as one of its notable places or features.
  • 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_69b3453c2a0c8190926b574c90766db9 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b3554fb28081909018eaecc0c5c230 completed March 13, 2026, 12:07 a.m.
NED1 Entity disambiguation (via context triple) batch_69b5f633a69c8190b062c2a78b0f8319 completed March 14, 2026, 11:58 p.m.
Created at: March 12, 2026, 11:30 p.m.