Triple
T12063017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Haven–New London |
E287220
|
entity |
| Predicate | passesThrough |
P225
|
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: [New Haven–New London, passesThrough, East Haven]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: East Haven Context triple: [New Haven–New London, passesThrough, 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.
New Haven
New Haven is a small city in central Kentucky known for its historic railroad heritage and proximity to the Kentucky Railway Museum.
-
E.
Naugatuck
Naugatuck is a borough and town in Connecticut known for its industrial history and location along the Naugatuck River.
- 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9043f82248190b05692aa0dc178a8 |
completed | April 10, 2026, 2:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f65e9693188190b22702216ca273e2 |
completed | May 2, 2026, 8:29 p.m. |
Created at: April 8, 2026, 9:48 p.m.