Triple

T4405112
Position Surface form Disambiguated ID Type / Status
Subject Southern Connecticut E93711 entity
Predicate contains P35 FINISHED
Object East Haven E598593 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 Haven | Statement: [Southern Connecticut, contains, East Haven]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: East Haven
Context triple: [Southern Connecticut, contains, East Haven]
  • A. East Haven chosen
    East Haven is a coastal town in southern Connecticut, located just east of the city of New Haven along Long Island Sound.
  • B. West Haven
    West Haven is a coastal city in southern Connecticut known for its public beaches and shoreline along Long Island Sound.
  • C. Hamden
    Hamden is a suburban town in south-central Connecticut, known for its proximity to New Haven and as the home of Quinnipiac University.
  • D. Naugatuck
    Naugatuck is a borough and town in Connecticut known for its industrial history and location along the Naugatuck River.
  • E. Stamford
    Stamford is a historic market town in eastern England renowned for its well-preserved medieval and Georgian architecture.
  • 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_69b345158c748190a2c040fce2da9980 completed March 12, 2026, 10:58 p.m.
NER Named-entity recognition batch_69b35488d5b8819087370dd77249aefb completed March 13, 2026, 12:04 a.m.
NED1 Entity disambiguation (via context triple) batch_69ca53f2b0b8819090ca8ee3721a9867 completed March 30, 2026, 10:44 a.m.
Created at: March 12, 2026, 11:28 p.m.