Triple

T7084700
Position Surface form Disambiguated ID Type / Status
Subject Tontine Crescent, Boston E165045 entity
Predicate locatedNear P294 FINISHED
Object Park Street E24761 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: Park Street | Statement: [Tontine Crescent, Boston, locatedNear, Park Street]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Park Street
Context triple: [Tontine Crescent, Boston, locatedNear, Park Street]
  • A. Park Street chosen
    Park Street is a major downtown Boston subway station and transfer hub on the Massachusetts Bay Transportation Authority (MBTA) system.
  • B. Park Street
    Park Street is a small village and residential community in Hertfordshire, England, situated near St Albans.
  • C. Park Street
    Park Street is one of the busiest and most prominent stations on the Kolkata Metro, serving the central commercial and entertainment district of the city.
  • D. Pine Street
    Pine Street is a major east–west thoroughfare in Philadelphia known for its historic rowhouses and role as a key residential and cultural corridor in Center City.
  • E. Pine Street
    Pine Street is a major east–west thoroughfare in downtown Seattle, Washington, known for its retail corridor and proximity to Pike Place Market.
  • 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_69c6887d98408190912b9580666b0c1d completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e511535c819098f60de54930380f completed March 27, 2026, 8:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69d316e50b548190b5f90a9753ad7cb0 completed April 6, 2026, 2:13 a.m.
Created at: March 27, 2026, 2:40 p.m.