Triple
T21412885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedale |
E528219
|
entity |
| Predicate | district |
P2709
|
FINISHED |
| Object | Hambleton |
—
|
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: Hambleton | Statement: [Bedale, district, Hambleton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hambleton Context triple: [Bedale, district, Hambleton]
-
A.
Hambleton
chosen
Hambleton is a largely rural district in North Yorkshire, England, known for its market towns and agricultural landscape.
-
B.
Hambleton Hills
Hambleton Hills is a range of hills in North Yorkshire, England, known for its scenic landscapes and role as a prominent feature of the North York Moors.
-
C.
Brockham
Brockham is a picturesque village in Surrey, England, known for its traditional village green and historic rural character.
-
D.
Hammerton
Hammerton is a village in North Yorkshire, England, served by a station on the Harrogate railway line between York and Leeds.
-
E.
Blunham
Blunham is a village in Bedfordshire, England, known for its rural setting near the River Ivel and historic parish church.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b20017d8819096b1a679edc8943a |
completed | April 22, 2026, 11:33 a.m. |
Created at: April 16, 2026, 5:44 p.m.