Triple
T5250198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Widford |
E118567
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Swinbrook |
E116748
|
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: Swinbrook | Statement: [Widford, locatedNear, Swinbrook]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Swinbrook Context triple: [Widford, locatedNear, Swinbrook]
-
A.
Swinbrook
chosen
Swinbrook is a small, picturesque village in rural Oxfordshire, England, known for its traditional stone cottages and historic church.
-
B.
Standlake
Standlake is a rural village in Oxfordshire, England, known for its historic parish church and location near the River Thames.
-
C.
Southwold
Southwold is a residential neighbourhood within the town of Bicester in Oxfordshire, England.
-
D.
Southwold
Southwold is a small seaside town and popular tourist resort on the North Sea coast of Suffolk, England, known for its pier, beach huts, and historic lighthouse.
-
E.
Eynsham
Eynsham is a historic village in Oxfordshire, England, known for its medieval abbey remains and its location near the River Thames between Oxford and Witney.
- 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.