Triple
T8920247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carterton |
E212394
|
entity |
| Predicate | hasNearbyTown |
P3883
|
FINISHED |
| Object | Burford |
E87872
|
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: Burford | Statement: [Carterton, hasNearbyTown, Burford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Burford Context triple: [Carterton, hasNearbyTown, Burford]
-
A.
Burford
chosen
Burford is a historic medieval market town in Oxfordshire, England, often regarded as one of the most picturesque settlements in the Cotswolds.
-
B.
Durford
Durford is a small settlement in West Sussex, England, situated in the countryside near the River Rother.
-
C.
Battisford
Battisford is a small rural village and civil parish located in the English county of Suffolk.
-
D.
Farlington
Farlington is a small rural village in North Yorkshire, England, situated near the River Foss and known for its historic parish church and agricultural surroundings.
-
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 (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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc664f099c8190be6d20a4574212ca |
completed | April 1, 2026, 12:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfba4f094c81909a30d3be640ac9e0 |
completed | April 3, 2026, 1:02 p.m. |
Created at: March 30, 2026, 6:56 p.m.