Triple
T3443937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Berkshire |
E72629
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Kintbury |
E211709
|
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: Kintbury | Statement: [West Berkshire, contains, Kintbury]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kintbury Context triple: [West Berkshire, contains, Kintbury]
-
A.
Kintbury
chosen
Kintbury is a rural village in Berkshire, England, known for its picturesque countryside setting and historic charm.
-
B.
Hawkenbury
Hawkenbury is a residential suburb and community area of Royal Tunbridge Wells in Kent, England.
-
C.
Buntingford
Buntingford is a small historic market town in Hertfordshire, England, known for its traditional high street and rural surroundings.
-
D.
Heytesbury
Heytesbury is a historic village and former parliamentary borough in Wiltshire, England.
-
E.
Pucklechurch
Pucklechurch is a village and civil parish in South Gloucestershire, England, known for its historic church and rural character near the city of Bristol.
- 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_69ad85b05c848190b7a28ceec2bd7b74 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adba2a605c8190a0eafdf6f25b1e38 |
completed | March 8, 2026, 6:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b360da33e081908630e3f29ea01530 |
completed | March 13, 2026, 12:56 a.m. |
Created at: March 8, 2026, 3:16 p.m.