Triple
T14736053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Ancholme |
E346209
|
entity |
| Predicate | nearbySettlement |
P350
|
FINISHED |
| Object | Wrawby |
E1047154
|
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: Wrawby | Statement: [River Ancholme, nearbySettlement, Wrawby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wrawby Context triple: [River Ancholme, nearbySettlement, Wrawby]
-
A.
Wrawby
chosen
Wrawby is a village in North Lincolnshire, England, known for its historic post mill and rural setting near the market town of Brigg.
-
B.
Wrey
Wrey is a variant spelling of the surname Wray, which is of English origin.
-
C.
Watnall
Watnall is a village in Nottinghamshire, England, historically associated with nearby Royal Air Force facilities and suburban communities near Nottingham.
-
D.
Ratby
Ratby is a village in Leicestershire, England, known for its historic parish church and proximity to the city of Leicester.
-
E.
Wainhill
Wainhill is a small hamlet in Oxfordshire, England, situated near the village of Chinnor in the Chiltern Hills.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec73114cc819088e1101b689fc70b |
completed | April 14, 2026, 11:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdfb8e0d488190851d73b75ba4c0a6 |
completed | May 8, 2026, 3:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.