Triple
T11919146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DH postcode area |
E283608
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | Consett |
E204561
|
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: Consett | Statement: [DH postcode area, hasPostTown, Consett]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Consett Context triple: [DH postcode area, hasPostTown, Consett]
-
A.
Consett
chosen
Consett is a town in north-west County Durham, England, historically known for its steelworks and industrial heritage.
-
B.
Peterlee
Peterlee is a post-war new town in North East England, established to serve nearby coal mining communities.
-
C.
Skelmersdale
Skelmersdale is a planned new town in West Lancashire, England, known for its extensive roundabout road system and post-war housing developments.
-
D.
Ormskirk
Ormskirk is a historic market town in West Lancashire, England, known for its traditional market, distinctive parish church, and proximity to both Liverpool and the surrounding countryside.
-
E.
Colne
Colne is a historic market town in Lancashire, England, known for its textile heritage and location near the Pennine hills.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8dff77481908cacf6ad03df34ac |
completed | April 10, 2026, 12:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f440247cf4819084567f6e1005ef04 |
completed | May 1, 2026, 5:54 a.m. |
Created at: April 8, 2026, 9:44 p.m.