Triple
T3949891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ollerton |
E84838
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | New Ollerton |
E84838
|
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: New Ollerton | Statement: [Ollerton, hasPart, New Ollerton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: New Ollerton Context triple: [Ollerton, hasPart, New Ollerton]
-
A.
Ollerton
chosen
Ollerton is a small town in Nottinghamshire, England, situated close to the historic Sherwood Forest associated with the legend of Robin Hood.
-
B.
Owerton
Owerton is an alternative spelling of the name Overton, which is used for various places and surnames in English-speaking regions.
-
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.
Loughton
Loughton is a suburban town in southeast England known for its proximity to Epping Forest and its role as a commuter hub within the London metropolitan area.
-
E.
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.
- 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_69aed934fbfc8190847068e4546de963 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef91227a8819097c3a5a206792382 |
completed | March 9, 2026, 4:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b533a4d3048190b63ad93a6ec87a48 |
completed | March 14, 2026, 10:08 a.m. |
Created at: March 9, 2026, 3:30 p.m.