Triple

T16603273
Position Surface form Disambiguated ID Type / Status
Subject Hingham, Massachusetts E403385 entity
Predicate locatedIn P40 FINISHED
Object South Shore E33301 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: South Shore | Statement: [Hingham, Massachusetts, locatedIn, South Shore]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: South Shore
Context triple: [Hingham, Massachusetts, locatedIn, South Shore]
  • A. South Shore chosen
    South Shore is a coastal suburban region south of Boston, Massachusetts, known for its residential communities, beaches, and commuter access to the city.
  • B. South Shore
    South Shore is a coastal region known for its surf-friendly beaches and breaks, popular among surfers and ocean enthusiasts.
  • C. South Shore
    South Shore is the suburban region located on the southern bank of the Saint Lawrence River opposite the Island of Montreal, known for its residential communities and commuter links to the city.
  • D. South Shore
    South Shore is a residential and lakefront community area on the South Side of Chicago known for its diverse population and views of Lake Michigan.
  • E. North Shore
    North Shore is a coastal region in northeastern Massachusetts known for its historic seaside towns, beaches, and proximity to Boston.
  • 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_69d883880d0c81908b5fcd454e767b60 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e35d77d97c8190a63330897e49a9c9 completed April 18, 2026, 10:31 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0075a67abc8190b0f29a9e4589befb completed May 10, 2026, 12:10 p.m.
Created at: April 10, 2026, 5:17 a.m.