Triple
T22502936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cod Beck Reservoir |
E556319
|
entity |
| Predicate | hasNearbySettlement |
P4647
|
FINISHED |
| Object | Swainby |
—
|
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: Swainby | Statement: [Cod Beck Reservoir, hasNearbySettlement, Swainby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Swainby Context triple: [Cod Beck Reservoir, hasNearbySettlement, Swainby]
-
A.
Swainby
chosen
Swainby is a small village in North Yorkshire, England, situated on the edge of the North York Moors and popular as a base for walking and outdoor activities.
-
B.
Scamblesby
Scamblesby is a small rural village in Lincolnshire, England, situated in the scenic Lincolnshire Wolds.
-
C.
Navenby
Navenby is a historic village and civil parish in Lincolnshire, England, known for its traditional architecture and rural character.
-
D.
Brocklesby
Brocklesby is a small rural town in the Riverina region of New South Wales, Australia, known for its agricultural community and historic railway connections.
-
E.
Hunmanby
Hunmanby is a village and civil parish in North Yorkshire, England, known for its historic charm and proximity to the seaside resort of Filey.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15d5a01888190ba65a05616b63cbe |
completed | April 29, 2026, 1:22 a.m. |
Created at: April 16, 2026, 8:50 p.m.