Triple
T7788099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAF North Weald |
E187297
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Epping |
E315899
|
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: Epping | Statement: [RAF North Weald, near, Epping]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Epping Context triple: [RAF North Weald, near, Epping]
-
A.
Epping
chosen
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
Chingford
Chingford is a suburban area in the London Borough of Waltham Forest, known as a residential district on the northeastern edge of Greater London near 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_69ca82af2d2c8190963861f5e0b8bf21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cae7e779ec8190b77296d9c2ac3210 |
completed | March 30, 2026, 9:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cbdea8e0ec8190a88dae9f0097ca16 |
completed | March 31, 2026, 2:48 p.m. |
Created at: March 30, 2026, 4:24 p.m.