Triple

T22987717
Position Surface form Disambiguated ID Type / Status
Subject William Strong E571957 entity
Predicate placeOfBirth P1 FINISHED
Object Somers, Connecticut NE NERFINISHED

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: Somers, Connecticut | Statement: [William Strong, placeOfBirth, Somers, Connecticut]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Somers, Connecticut
Context triple: [William Strong, placeOfBirth, Somers, Connecticut]
  • A. Somers, Connecticut chosen
    Somers, Connecticut is a small New England town in north-central Connecticut known for its rural character and location near the Massachusetts border.
  • B. Somers
    Somers is a small lakeside community in northwestern Montana, situated on the northern shore of Flathead Lake in the Flathead Valley.
  • C. Somers
    Somers is a surname of English origin borne by various notable individuals across fields such as politics, literature, and entertainment.
  • D. Somers
    Somers is a village in Kenosha County, Wisconsin, known for hosting the University of Wisconsin–Parkside campus.
  • E. Black Rock, Connecticut
    Black Rock, Connecticut is a coastal neighborhood in Bridgeport known historically as a maritime and shipbuilding community.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e245b535808190adef8a9df3c584db completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1829b4ea88190bc1a01183df7a1bb completed April 29, 2026, 4:01 a.m.
Created at: April 17, 2026, 3:49 p.m.