Triple
T21551186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charmouth |
E531763
|
entity |
| Predicate | hasNearbyTown |
P3883
|
FINISHED |
| Object | Bridport |
—
|
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: Bridport | Statement: [Charmouth, hasNearbyTown, Bridport]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bridport Context triple: [Charmouth, hasNearbyTown, Bridport]
-
A.
Bridport
chosen
Bridport is a historic market town in southwest England known for its rope-making heritage and proximity to the Jurassic Coast.
-
B.
Holyport
Holyport is a village in Berkshire, England, known for its traditional green, historic pubs, and proximity to the towns of Windsor and Maidenhead.
-
C.
Stourmouth
Stourmouth is a small rural village in Kent, England, situated near the River Stour and known for its historic church and countryside setting.
-
D.
Studland
Studland is a coastal village in Dorset, England, known for its sandy beaches, heathland nature reserve, and scenic views across Studland Bay.
-
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 (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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeb59258b88190966c18f1f519dad6 |
completed | April 27, 2026, 1:02 a.m. |
Created at: April 16, 2026, 6:29 p.m.