Triple
T12537004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Blakenham |
E299718
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Claydon |
E301430
|
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: Claydon | Statement: [Great Blakenham, locatedNear, Claydon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Claydon Context triple: [Great Blakenham, locatedNear, Claydon]
-
A.
Claydon
chosen
Claydon is a village and civil parish located in the county of Suffolk in eastern England.
-
B.
Claydon
Claydon is a small village in Buckinghamshire, England, known for its rural setting and proximity to historic railway sites.
-
C.
Chaldon
Chaldon is a small historic village in Surrey, England, noted for its ancient church and rural character within the Tandridge district.
-
D.
Clayhall
Clayhall is a suburban residential district in northeast London, known for its parks, schools, and diverse community.
-
E.
Reydon
Reydon is a village and civil parish in the English county of Suffolk, located near the coastal town of Southwold.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d9546ebf508190ae54857e4289c6e4 |
completed | April 10, 2026, 7:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f65eb10618819092540de09997a0c5 |
completed | May 2, 2026, 8:29 p.m. |
Created at: April 8, 2026, 9:57 p.m.