Triple

T11938379
Position Surface form Disambiguated ID Type / Status
Subject Peabody, Massachusetts E284109 entity
Predicate formerName P65 FINISHED
Object South Danvers E89311 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 Danvers | Statement: [Peabody, Massachusetts, formerName, South Danvers]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: South Danvers
Context triple: [Peabody, Massachusetts, formerName, South Danvers]
  • A. South Danvers chosen
    South Danvers was the former name of the city now known as Peabody, Massachusetts, a North Shore community near Boston.
  • B. Witham
    Witham is a town in the county of Essex, England, known as a residential and commuter community between Chelmsford and Colchester.
  • C. Porter Valley
    Porter Valley is a scenic valley in Sheffield, England, known for its wooded landscapes, historic industrial sites, and popular walking routes along the Porter Brook.
  • D. Mill Plain
    Mill Plain is a major arterial corridor in Vancouver, Washington, serving as a key route for local traffic, transit, and commercial activity.
  • E. Pocasset
    Pocasset is a coastal village on Cape Cod in Massachusetts known for its beaches, marinas, and residential seaside character.
  • 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_69d6ab2ce9c48190b5d39511b524f666 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d903094218819092e11b273d87de65 completed April 10, 2026, 2:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69f4409a40dc81909d87c50601b98b78 completed May 1, 2026, 5:56 a.m.
Created at: April 8, 2026, 9:45 p.m.