Triple
T10088054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chorleywood |
E215269
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Rickmansworth |
E368764
|
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: Rickmansworth | Statement: [Chorleywood, locatedNear, Rickmansworth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rickmansworth Context triple: [Chorleywood, locatedNear, Rickmansworth]
-
A.
Rickmansworth
chosen
Rickmansworth is a small town in south-west Hertfordshire, England, known for its canals, lakes, and role as a commuter suburb of London.
-
B.
Harmondsworth
Harmondsworth is a village in the London Borough of Hillingdon, England, known for its historic Great Barn and proximity to Heathrow Airport.
-
C.
Welwyn Hatfield
Welwyn Hatfield is a local government district and borough in Hertfordshire, England, that includes the towns of Welwyn Garden City and Hatfield.
-
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.
Welwyn
Welwyn is a historic village and civil parish in Hertfordshire, England, known for its Roman heritage and picturesque rural character.
- 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_69ca83a1eed081908b2e9580f2ebeea7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd04875748190a81d1e9ad68dda96 |
completed | April 2, 2026, 2:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3c79bc53481908552af9ebd582edf |
completed | April 18, 2026, 6:04 p.m. |
Created at: March 30, 2026, 9:01 p.m.