Triple
T15184423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Route 101 bridge in Milford |
E362829
|
entity |
| Predicate | town |
P3385
|
FINISHED |
| Object | Milford |
E362828
|
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: [Route 101 bridge in Milford, town, Milford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Milford Context triple: [Route 101 bridge in Milford, town, Milford]
-
A.
Milford
chosen
Milford is a New Hampshire town in Hillsborough County known historically for its mill industry and its location along the Souhegan River.
-
B.
Milford
Milford is a locality associated with the city of Salisbury, likely recognized as one of its notable places or features.
-
C.
Milford
Milford is a small town located within Otsego County in the central region of New York State.
-
D.
Milford
Milford is a small town in County Donegal, Ireland, known as a local service and residential center for the surrounding rural area.
-
E.
Milford
Milford is a small town located in Maine’s Penobscot Valley region, known for its rural character and proximity to the Penobscot 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006674c088190ba635a78c30f5637 |
completed | April 15, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fec893f1e08190a192b7b9b80484e8 |
completed | May 9, 2026, 5:39 a.m. |
Created at: April 10, 2026, 3:09 a.m.