Triple
T6871980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hertsmere |
E158570
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Shenley |
E211879
|
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: Shenley | Statement: [Hertsmere, containsSettlement, Shenley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shenley Context triple: [Hertsmere, containsSettlement, Shenley]
-
A.
Shenley
chosen
Shenley is a village and civil parish in the county of Hertfordshire in southern England, known for its residential character and proximity to London.
-
B.
Irstead
Irstead is a small village in Norfolk, England, situated within the scenic Norfolk Broads wetland area.
-
C.
Knaphill
Knaphill is a suburban village in Surrey, England, forming part of the borough of Woking.
-
D.
Hockley
Hockley is a village in Essex, England, known for its residential character and rail links to London and Southend.
-
E.
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.
- 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_69c68831e3648190a643c328122e4d43 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d8ac04e08190aa8011c0ade9d509 |
completed | March 27, 2026, 7:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c742af0df88190bb23b7495c279e08 |
completed | March 28, 2026, 2:53 a.m. |
Created at: March 27, 2026, 2:22 p.m.