Triple
T2843871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Haven County |
E62535
|
entity |
| Predicate | containsCity |
P294
|
FINISHED |
| Object | Milford |
E112061
|
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: Milford | Statement: [New Haven County, containsCity, Milford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Milford Context triple: [New Haven County, containsCity, Milford]
-
A.
Milford
chosen
Milford is a coastal city in southern Connecticut known for its beaches and harbors along Long Island Sound.
-
B.
Milford
Milford is a village in Surrey, England, situated near the town of Godalming.
-
C.
Milford
Milford is a town in central Massachusetts known for its historic granite quarries and suburban residential character.
-
D.
Winslow
Winslow is the main commercial and residential hub of Bainbridge Island, Washington, known for its downtown shops, restaurants, and ferry terminal connecting to Seattle.
-
E.
Winslow
Winslow is an English-origin surname historically associated with early colonial families in New England.
- 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_69ab4c3d16bc81908b3a1c98fbd287fe |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf1a07508190be35fe85733ddeed |
completed | March 7, 2026, 8:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afe8d570388190b4ed81ace605c6c3 |
completed | March 10, 2026, 9:48 a.m. |
Created at: March 6, 2026, 10:02 p.m.