Triple

T17965000
Position Surface form Disambiguated ID Type / Status
Subject Belmont, New Hampshire E449179 entity
Predicate originalName P65 FINISHED
Object Upper Gilmanton E627247 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: Upper Gilmanton | Statement: [Belmont, New Hampshire, originalName, Upper Gilmanton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Upper Gilmanton
Context triple: [Belmont, New Hampshire, originalName, Upper Gilmanton]
  • A. Westermoor
    Westermoor is a small municipality in the district of Steinburg in Schleswig-Holstein, northern Germany.
  • B. Mill Plain
    Mill Plain is a major arterial corridor in Vancouver, Washington, serving as a key route for local traffic, transit, and commercial activity.
  • C. Martinsborough
    Martinsborough was the original name of the city now known as Greenville in eastern North Carolina.
  • D. Gilmanton, New Hampshire chosen
    Gilmanton, New Hampshire is a rural town in Belknap County known for its historic New England character and scenic lakes-region setting.
  • E. Witham
    Witham is a town in the county of Essex, England, known as a residential and commuter community between Chelmsford and Colchester.
  • 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_69d8b9f9927c8190a006110c8b996e61 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4b136e4088190ac97fd92dc84a4b9 completed April 19, 2026, 10:40 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0330100f048190aba7448d9891cfdc completed May 12, 2026, 1:50 p.m.
Created at: April 10, 2026, 10:22 a.m.