Triple
T14691748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnham Beeches |
E345051
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Farnham Common |
E1003865
|
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: Farnham Common | Statement: [Burnham Beeches, locatedNear, Farnham Common]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Farnham Common Context triple: [Burnham Beeches, locatedNear, Farnham Common]
-
A.
Farnham Common
chosen
Farnham Common is a village in Buckinghamshire, England, known for its proximity to Burnham Beeches woodland and its affluent residential character.
-
B.
Oldland Common
Oldland Common is a village and residential area in South Gloucestershire, England, known for its suburban character and proximity to Bristol.
-
C.
Chelsham Common
Chelsham Common is a village green and open common land in the rural parish of Chelsham in Surrey, England.
-
D.
Burghfield Common
Burghfield Common is a large residential village in West Berkshire, England, known for its commuter links to Reading and surrounding towns.
-
E.
Hungerford Common
Hungerford Common is a large open area of common land near the town of Hungerford in Berkshire, England, known for its grazing, walking paths, and wildlife.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb585d46c81908d6964130914cec4 |
completed | April 14, 2026, 9:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdf08274ac8190b5ba0752d36a690b |
completed | May 8, 2026, 2:17 p.m. |
Created at: April 10, 2026, 1:28 a.m.