Triple
T7682874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairford |
E174038
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | Fairford |
E174038
|
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: Fairford | Statement: [Fairford, hasPostTown, Fairford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fairford Context triple: [Fairford, hasPostTown, Fairford]
-
A.
Fairford
chosen
Fairford is a small market town in Gloucestershire, England, known for its historic wool church and proximity to RAF Fairford airbase.
-
B.
Highworth
Highworth is a historic market town in Wiltshire, England, known for its elevated position and traditional architecture.
-
C.
Belchford
Belchford is a small rural village in eastern England, situated within the scenic, rolling countryside of the Lincolnshire Wolds.
-
D.
Sharneyford
Sharneyford is a small settlement in Lancashire, England, situated within the Rossendale Valley near the border with West Yorkshire.
-
E.
Pyrford
Pyrford is a village in Surrey, England, known for its historic church, green spaces, and residential character near the town of Woking.
- 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_69c6995840408190a19de6c51090f46f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7021ce1308190be58d17ebaafa6ae |
completed | March 27, 2026, 10:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8a25304b88190920c2e4908925ce2 |
completed | March 29, 2026, 3:53 a.m. |
Created at: March 27, 2026, 4:01 p.m.