Triple
T3471859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berkhamsted |
E73278
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | BERKHAMSTED |
E73278
|
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: BERKHAMSTED | Statement: [Berkhamsted, hasPostTown, BERKHAMSTED]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BERKHAMSTED Context triple: [Berkhamsted, hasPostTown, BERKHAMSTED]
-
A.
Berkhamsted
chosen
Berkhamsted is a historic market town in Hertfordshire, England, known for its medieval castle remains and role as a commuter hub northwest of London.
-
B.
Little Berkhamsted
Little Berkhamsted is a small rural village and civil parish in the county of Hertfordshire, England.
-
C.
Harrow
Harrow is a suburban district in northwest London, England, known for its historic town center and the prestigious Harrow School.
-
D.
Chobham
Chobham is a village and civil parish in Surrey, England, known for its rural character, common land, and historic buildings.
-
E.
Hunsdon
Hunsdon is a rural village and civil parish in Hertfordshire, England, known for its historic airfield and countryside setting.
- 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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb3cc8488190b97c732e3f600a90 |
completed | March 8, 2026, 6:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b36810958c81908982e0ef996dc480 |
completed | March 13, 2026, 1:27 a.m. |
Created at: March 8, 2026, 3:17 p.m.