Triple
T5250206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of St Oswald |
E118567
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Widford |
E197919
|
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: Widford | Statement: [Church of St Oswald, locatedIn, Widford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Widford Context triple: [Church of St Oswald, locatedIn, Widford]
-
A.
Widford
Widford is a small rural village in Oxfordshire, England, known for its historic church and picturesque countryside setting.
-
B.
Widford
chosen
Widford is a small village and civil parish in East Hertfordshire, England, known for its rural character and historic parish church.
-
C.
Wangford
Wangford is a small rural village and civil parish located in the English county of Suffolk.
-
D.
Belchford
Belchford is a small rural village in eastern England, situated within the scenic, rolling countryside of the Lincolnshire Wolds.
-
E.
Fairford
Fairford is a small market town in Gloucestershire, England, known for its historic wool church and proximity to RAF Fairford airbase.
- 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b79ae0c81908a9b8614f6886259 |
completed | March 20, 2026, 4:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69befe6cd9ac81909a97ff26d061746a |
completed | March 21, 2026, 8:24 p.m. |
Created at: March 20, 2026, 1:50 p.m.