Triple
T19302439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Coln |
E482734
|
entity |
| Predicate | nearbySettlement |
P350
|
FINISHED |
| Object | Fairford |
—
|
NE NERFINISHED |
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: [River Coln, nearbySettlement, Fairford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fairford Context triple: [River Coln, nearbySettlement, 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.
Britford
Britford is a small village and civil parish in Wiltshire, England, situated just southeast of Salisbury and known for its historic church and rural character.
-
C.
Highworth
Highworth is a historic market town in Wiltshire, England, known for its elevated position and traditional architecture.
-
D.
Wyndford
Wyndford is a residential neighborhood in the Maryhill area of Glasgow, Scotland, known for its post-war housing estates and close-knit community.
-
E.
Belchford
Belchford is a small rural village in eastern England, situated within the scenic, rolling countryside of the Lincolnshire Wolds.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc8add788190aed98bcbad518808 |
completed | April 20, 2026, 10:14 a.m. |
Created at: April 10, 2026, 1:31 p.m.