Triple
T10976620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cranham, Essex |
E259386
|
entity |
| Predicate | hasNeighbour |
P5707
|
FINISHED |
| Object | North Ockendon |
E272459
|
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: North Ockendon | Statement: [Cranham, Essex, hasNeighbour, North Ockendon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: North Ockendon Context triple: [Cranham, Essex, hasNeighbour, North Ockendon]
-
A.
Ockendon
chosen
Ockendon is a settlement in the borough of Thurrock in Essex, England, known for its suburban character and proximity to London.
-
B.
Epping
Epping is a market town in the Epping Forest district of Essex, England, known for its historic high street and proximity to the ancient Epping Forest.
-
C.
Epping
Epping is a suburb in Melbourne, Australia, known for its residential communities, shopping facilities, and role as a transport hub in the city's northern corridor.
-
D.
Hornchurch
Hornchurch is a suburban town in East London, England, known for its residential character and historic links to RAF Hornchurch.
-
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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d771f5bef481909043656c571fda89 |
completed | April 9, 2026, 9:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e2d7bcea448190b09906c79de67496 |
completed | April 18, 2026, 1 a.m. |
Created at: April 8, 2026, 9:24 p.m.