Triple

T1135017
Position Surface form Disambiguated ID Type / Status
Subject Lynn, Massachusetts E23118 entity
Predicate hasNeighborhood P40 FINISHED
Object East Lynn E23118 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: East Lynn | Statement: [Lynn, Massachusetts, hasNeighborhood, East Lynn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: East Lynn
Context triple: [Lynn, Massachusetts, hasNeighborhood, East Lynn]
  • A. Lynn, Massachusetts chosen
    Lynn, Massachusetts is a historic coastal city just north of Boston known for its industrial past, diverse population, and oceanfront parks.
  • B. North Lynn
    North Lynn is a residential and industrial area within the town of King’s Lynn in Norfolk, England.
  • C. West Newton
    West Newton is a residential village and historic neighborhood within the city of Newton, Massachusetts.
  • D. West Newton
    West Newton is a small village in Norfolk, England, known for its rural character and proximity to the royal Sandringham Estate.
  • E. Southborough
    Southborough is a small town in Kent, England, situated between Tunbridge Wells and Tonbridge and known for its residential character and green spaces.
  • 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_69a493ec75988190b63a11bafaec29b4 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4bbfffaa48190b2534ff4da3544ce completed March 1, 2026, 10:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad293648d08190a1c15fe677aa7b8c completed March 8, 2026, 7:45 a.m.
Created at: March 1, 2026, 7:44 p.m.