Triple
T4098174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burford |
E87872
|
entity |
| Predicate | postalTown |
P2711
|
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: [Burford, postalTown, Burford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Burford Context triple: [Burford, postalTown, 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.
Battisford
Battisford is a small rural village and civil parish located in the English county of Suffolk.
-
C.
Burtonwood
Burtonwood is a village in Cheshire, England, historically associated with coal mining and the former RAF Burtonwood airbase.
-
D.
Newbourne
Newbourne is a small rural village and civil parish in the English county of Suffolk, known for its countryside setting and traditional village character.
-
E.
Burham
Burham is a village in Kent, England, situated near the River Medway and known for its rural character and historic parish church.
- 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_69aed94564cc8190a9c1457daedb6e7f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefce017708190a4d33753fd32a7bb |
completed | March 9, 2026, 5:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b56b725788819091c6aaeccfb86964 |
completed | March 14, 2026, 2:06 p.m. |
Created at: March 9, 2026, 3:40 p.m.