Triple
T2548079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capability Brown |
E57951
|
entity |
| Predicate | residence |
P75
|
FINISHED |
| Object | Fenstanton |
E229885
|
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: Fenstanton | Statement: [Capability Brown, residence, Fenstanton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fenstanton Context triple: [Capability Brown, residence, Fenstanton]
-
A.
Fenstanton
chosen
Fenstanton is a village and civil parish in Cambridgeshire, England, situated near the River Great Ouse between Huntingdon and St Ives.
-
B.
Yattendon
Yattendon is a small village and civil parish in Berkshire, England, known for its rural character and historic buildings.
-
C.
Ingatestone
Ingatestone is a historic village and civil parish in southeast England known for its traditional architecture and commuter links to London.
-
D.
Sharneyford
Sharneyford is a small settlement in Lancashire, England, situated within the Rossendale Valley near the border with West Yorkshire.
-
E.
Grimston
Grimston is a village and civil parish in the English county of Norfolk, known for its historic church and rural setting near King’s Lynn.
- 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2e672948190bb7fe9b47535a172 |
completed | March 7, 2026, 7:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af5d0e6e188190be190965cc02838e |
completed | March 9, 2026, 11:51 p.m. |
Created at: March 6, 2026, 9:47 p.m.