Triple

T2884995
Position Surface form Disambiguated ID Type / Status
Subject Yale Repertory Theatre E59483 entity
Predicate city 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: [Yale Repertory Theatre, city, New Haven]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: New Haven
Context triple: [Yale Repertory Theatre, city, 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. West Haven
    West Haven is a coastal city in southern Connecticut known for its public beaches and shoreline along Long Island Sound.
  • D. 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.
  • E. Hamden
    Hamden is a suburban town in south-central Connecticut, known for its proximity to New Haven and as the home of Quinnipiac University.
  • 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_69ab4ac739188190a112f42a5a69c951 completed March 6, 2026, 9:44 p.m.
NER Named-entity recognition batch_69abe04476588190b0db0880e14c79b5 completed March 7, 2026, 8:22 a.m.
NED1 Entity disambiguation (via context triple) batch_69c7239e1ea481908c64d8a2d600aa30 completed March 28, 2026, 12:41 a.m.
Created at: March 6, 2026, 10:03 p.m.