Triple
T16471108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Somerset and Dorset Joint Railway |
E400060
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Blandford Forum |
E42251
|
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: Blandford Forum | Statement: [Somerset and Dorset Joint Railway, passesThrough, Blandford Forum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Blandford Forum Context triple: [Somerset and Dorset Joint Railway, passesThrough, Blandford Forum]
-
A.
Blandford Forum
chosen
Blandford Forum is a historic market town on the River Stour in Dorset, England, noted for its Georgian architecture and rural surroundings.
-
B.
Blyford
Blyford is a small rural village located in the English county of Suffolk.
-
C.
Asheldham
Asheldham is a small rural village and civil parish in the Maldon District of Essex, England.
-
D.
Grindon
Grindon is a residential suburb of Sunderland in the Wearside area of North East England.
-
E.
Southwold
Southwold is a residential neighbourhood within the town of Bicester in Oxfordshire, 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32dd0d2fc81909b68b5afb00f192f |
completed | April 18, 2026, 7:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a004f5af4308190bd023624de35027f |
completed | May 10, 2026, 9:26 a.m. |
Created at: April 10, 2026, 5:11 a.m.