Triple
T8899262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kimpton |
E211883
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Harpenden |
E227748
|
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: Harpenden | Statement: [Kimpton, locatedNear, Harpenden]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Harpenden Context triple: [Kimpton, locatedNear, Harpenden]
-
A.
Harpenden
chosen
Harpenden is a commuter town in southern England known for its green spaces and affluent residential character.
-
B.
Bovingdon
Bovingdon is a large village and civil parish in Hertfordshire, England, known for its historic airfield and proximity to the town of Hemel Hempstead.
-
C.
Cheshunt
Cheshunt is a town in Hertfordshire, England, situated just north of London and known as a commuter hub with rail links into the capital.
-
D.
Hoddesdon
Hoddesdon is a historic market town in southern England known for its traditional high street, commuter links to London, and proximity to the River Lea.
-
E.
Bennetts End
Bennetts End is a residential area and suburb located within the county of Hertfordshire in England.
- 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_69ca83918d3081909b326fa3750cb8c8 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc64278b208190afc3dec64ecdb0f5 |
completed | April 1, 2026, 12:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfc92e668c819086e694f92c04add6 |
completed | April 3, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:54 p.m.