Triple
T19285423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bilston |
E482296
|
entity |
| Predicate | hasSuburb |
P747
|
FINISHED |
| Object | Ettingshall |
E1150165
|
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: Ettingshall | Statement: [Bilston, hasSuburb, Ettingshall]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ettingshall Context triple: [Bilston, hasSuburb, Ettingshall]
-
A.
Ringshall
Ringshall is a small rural village and civil parish located in the county of Suffolk in eastern England.
-
B.
Blakenhall
chosen
Blakenhall is a district of Wolverhampton in the West Midlands, England, known as a residential urban area with local community and sporting facilities.
-
C.
Coltishall
Coltishall is a village in Norfolk, England, known as a gateway to the Norfolk Broads and for its riverside setting and historic charm.
-
D.
Hensingham
Hensingham is a residential suburb of Whitehaven in Cumbria, England, known for its local community facilities and proximity to the town’s centre.
-
E.
Hellingly
Hellingly is a village and civil parish in East Sussex, England, known for its rural character and historic parish church.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc0152d48190b92272d4c7caa708 |
completed | April 20, 2026, 10:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a070e80d5b08190b304a874dac3d21d |
completed | May 15, 2026, 12:16 p.m. |
Created at: April 10, 2026, 1:30 p.m.