Triple
T12880929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yarrow Valley |
E308090
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Yarrowford |
E685967
|
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: Yarrowford | Statement: [Yarrow Valley, hasSettlement, Yarrowford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yarrowford Context triple: [Yarrow Valley, hasSettlement, Yarrowford]
-
A.
Yarrowford
chosen
Yarrowford is a small village in the Scottish Borders region of Scotland, situated in the Yarrow Valley near the River Yarrow.
-
B.
Sharneyford
Sharneyford is a small settlement in Lancashire, England, situated within the Rossendale Valley near the border with West Yorkshire.
-
C.
Belchford
Belchford is a small rural village in eastern England, situated within the scenic, rolling countryside of the Lincolnshire Wolds.
-
D.
Shillingford
Shillingford is a small village in South Oxfordshire, England, known for its rural setting near the River Thames and proximity to the town of Benson.
-
E.
Yelford
Yelford is a small rural settlement in Oxfordshire, England, known for its historic manor house and traditional village character.
- 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_69d7bdf69bc48190af6c2621f28ca351 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d970fc1e488190a0c48039f6213e62 |
completed | April 10, 2026, 9:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6a55393a88190a88c9357a6db5aec |
completed | May 3, 2026, 1:30 a.m. |
Created at: April 9, 2026, 5:39 p.m.