Triple
T21487466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weymouth Bay |
E530150
|
entity |
| Predicate | hasNearbySettlement |
P4647
|
FINISHED |
| Object | Preston, Dorset |
—
|
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: Preston, Dorset | Statement: [Weymouth Bay, hasNearbySettlement, Preston, Dorset]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Preston, Dorset Context triple: [Weymouth Bay, hasNearbySettlement, Preston, Dorset]
-
A.
Preston (Dorset)
chosen
Preston (Dorset) is a coastal village and suburb of Weymouth in Dorset, England, known for its proximity to Weymouth Bay and the Jurassic Coast.
-
B.
Preston, Sussex, England
Preston, Sussex, England is a historic village and former parish now part of the city of Brighton and Hove on England’s south coast.
-
C.
Preston
Preston is a small city in Webster County, Georgia, serving as the county seat and local administrative center.
-
D.
Preston
Preston is a locality within the Dover District of Kent, England, known as a small rural village community.
-
E.
Preston
Preston is a residential area and suburb within the Metropolitan Borough of North Tyneside in North East England.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea37e25c81909ae185fcab19bc4b |
completed | April 23, 2026, 9:45 a.m. |
Created at: April 16, 2026, 6:22 p.m.