Triple
T3962170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broadstone, Dorset |
E85929
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Poole |
E238401
|
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: Poole | Statement: [Broadstone, Dorset, locatedNear, Poole]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Poole Context triple: [Broadstone, Dorset, locatedNear, Poole]
-
A.
Poole
chosen
Poole is a coastal town and seaport in Dorset, England, known for its large natural harbour and maritime activities.
-
B.
Bournemouth
Bournemouth is a large coastal resort town on England’s south coast, known for its sandy beaches, tourism, and role as a regional commercial and transport hub.
-
C.
Bridgwater
Bridgwater is a historic market town in Somerset, England, known for its maritime heritage and role in regional trade and industry.
-
D.
Yeovil
Yeovil is a town in Somerset, England, known historically for its aircraft and defence industries and serving as a commercial and service hub for the surrounding rural area.
-
E.
Bideford
Bideford is a historic port town on the River Torridge in North Devon, England, known for its maritime heritage and role as a local commercial center.
- 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_69aed93a96908190bcbdbfa718f155bd |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef9617adc8190874b97a612fa7c72 |
completed | March 9, 2026, 4:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b67b9e1b4081909f53466a603d7061 |
completed | March 15, 2026, 9:27 a.m. |
Created at: March 9, 2026, 3:31 p.m.