Triple
T16534006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raynham |
E401640
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Bridgewater |
—
|
NE NERFINISHED |
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: Bridgewater | Statement: [Raynham, borders, Bridgewater]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bridgewater Context triple: [Raynham, borders, Bridgewater]
-
A.
Bridgewater
Bridgewater is a town in Tasmania, Australia, situated on the banks of the Derwent River and known as a residential and transport hub north of Hobart.
-
B.
Bridgewater
Bridgewater is a historic English place name associated with the peerage title Earl of Bridgewater.
-
C.
Bridgewater
Bridgewater is a small city in McCook County, South Dakota, known as a rural Midwestern community with an agricultural-based local economy.
-
D.
Bridgewater
Bridgewater is a commuter rail station in Bridgewater, Massachusetts, served by the MBTA's Middleborough/Lakeville Line.
-
E.
Bridgewater
Bridgewater is a small township in the Adelaide Hills region of South Australia, known for its leafy surroundings and semi-rural residential character.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
Provenance (2 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32eda42548190be61efb25a44a554 |
completed | April 18, 2026, 7:12 a.m. |
Created at: April 10, 2026, 5:15 a.m.