Triple
T6587934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cookham Dean |
E159273
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | Cookham |
E280116
|
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: Cookham | Statement: [Cookham Dean, partOf, Cookham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cookham Context triple: [Cookham Dean, partOf, Cookham]
-
A.
Cookham
chosen
Cookham is a picturesque English village on the River Thames in Berkshire, noted for its historic charm and association with painter Stanley Spencer.
-
B.
Cookham Dean
Cookham Dean is a picturesque village in Berkshire, England, known for its rural charm and association with author Kenneth Grahame.
-
C.
Burnham Norton
Burnham Norton is a small coastal village in Norfolk, England, known for its historic church and saltmarsh landscape near the North Sea.
-
D.
Pangbourne
Pangbourne is a picturesque village on the River Thames in Berkshire, England, known for its literary associations and scenic rural charm.
-
E.
Eynsham
Eynsham is a historic village in Oxfordshire, England, known for its medieval abbey remains and its location near the River Thames between Oxford and Witney.
- 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_69c688366ce8819083f8883983c0df92 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6aeb0e9d88190aa861e742ff6804e |
completed | March 27, 2026, 4:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6cbb00cc48190a49afdb82a267043 |
completed | March 27, 2026, 6:25 p.m. |
Created at: March 27, 2026, 1:55 p.m.