Triple

T10636038
Position Surface form Disambiguated ID Type / Status
Subject Temple Street (New Haven) E250582 entity
Predicate locatedIn P40 FINISHED
Object New Haven E14903 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: New Haven | Statement: [Temple Street (New Haven), locatedIn, New Haven]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: New Haven
Context triple: [Temple Street (New Haven), locatedIn, New Haven]
  • A. New Haven, Connecticut chosen
    New Haven, Connecticut is a historic coastal city in southern New England best known as the home of Yale University and a major center of education, culture, and research.
  • B. Hartford
    Hartford is the capital city of Connecticut and a historic center of insurance, government, and culture in the northeastern United States.
  • C. Hartford
    Hartford is a small city in eastern South Dakota that functions as a suburban community within the greater Sioux Falls metropolitan area.
  • D. West Haven
    West Haven is a coastal city in southern Connecticut known for its public beaches and shoreline along Long Island Sound.
  • E. New Haven–New London
    New Haven–New London is a regional rail corridor in Connecticut connecting the coastal cities of New Haven and New London along Long Island Sound.
  • 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_69d6aa5993448190a493b790b8f85010 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6dfad9dbc81909a4f78d93ecfaa20 completed April 8, 2026, 11:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69e482d55a04819090d95f7a4abb6e29 completed April 19, 2026, 7:23 a.m.
Created at: April 8, 2026, 9:03 p.m.