Triple
T12047258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CM postcode area |
E286818
|
entity |
| Predicate | covers |
P1393
|
FINISHED |
| Object | Wickford |
E168880
|
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: Wickford | Statement: [CM postcode area, covers, Wickford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wickford Context triple: [CM postcode area, covers, Wickford]
-
A.
Wickford
chosen
Wickford is a town in the county of Essex in the East of England, known as a commuter settlement with local shopping areas and access to London.
-
B.
Wereham
Wereham is a small rural village in Norfolk, England, known for its historic church and traditional village green.
-
C.
Winsloe
Winsloe is a variant spelling of the English surname and place name Winslow.
-
D.
Rayleigh and Wickford
Rayleigh and Wickford is a UK parliamentary constituency in Essex represented in the House of Commons.
-
E.
Willington
Willington is a village and civil parish in South Derbyshire, England, known for its riverside location on the Trent and Mersey Canal and nearby power station landmarks.
- 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_69d6ab4780948190bdb9f7620c2ac27e |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d904211b588190bfc7603e5b33dcb7 |
completed | April 10, 2026, 2:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f49dc459308190bc88cb550e1d5b86 |
completed | May 1, 2026, 12:34 p.m. |
Created at: April 8, 2026, 9:47 p.m.