Triple

T8405476
Position Surface form Disambiguated ID Type / Status
Subject Hingham Harbor E198485 entity
Predicate accessibleFrom P1985 FINISHED
Object Route 3A E446600 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: Route 3A | Statement: [Hingham Harbor, accessibleFrom, Route 3A]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Route 3A
Context triple: [Hingham Harbor, accessibleFrom, Route 3A]
  • A. Route 3A chosen
    Route 3A is a state highway in Massachusetts that generally parallels Route 3, connecting various coastal and suburban communities south and north of Boston.
  • B. Route 3
    Route 3 is a major Costa Rican highway that passes through the district of Uruca and connects key urban areas in the country’s Central Valley.
  • C. Route 3
    Route 3 is a major east–west highway in northern New Jersey that connects the New Jersey Turnpike area to the Lincoln Tunnel approach into New York City.
  • D. Route 3
    Route 3 is a major north–south highway in Massachusetts that links the Boston area to the South Shore and Cape Cod while also connecting with key regional routes such as the Lowell Connector.
  • E. Route 30
    Route 30 is a major east–west highway in Massachusetts that serves as a key commercial and commuter corridor through communities such as Framingham.
  • 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_69ca8310df9c8190b25f16161cca3e41 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cb8312941c8190af0b2def0a4e02be completed March 31, 2026, 8:17 a.m.
NED1 Entity disambiguation (via context triple) batch_69ce02f8596c8190a61b6f1ffd5a609c completed April 2, 2026, 5:47 a.m.
Created at: March 30, 2026, 6:05 p.m.