Triple
T17774147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Borough of Walsall |
E443720
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Willenhall |
E927318
|
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: Willenhall | Statement: [Metropolitan Borough of Walsall, contains, Willenhall]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Willenhall Context triple: [Metropolitan Borough of Walsall, contains, Willenhall]
-
A.
Willenhall
chosen
Willenhall is a town in the West Midlands of England, historically known for its lock and key manufacturing industry.
-
B.
Hellingly
Hellingly is a village and civil parish in East Sussex, England, known for its rural character and historic parish church.
-
C.
Lyonshall
Lyonshall is a rural village and civil parish in Herefordshire, England, known for its historic castle remains and agricultural surroundings.
-
D.
Kilndown
Kilndown is a small rural village in Kent, England, known for its historic church and woodland surroundings.
-
E.
Windlesham
Windlesham is a village and civil parish in the Surrey Heath district of Surrey, England, known for its affluent residential character and leafy surroundings.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4871af4248190aed2b3bd42433771 |
completed | April 19, 2026, 7:41 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a02efc7a3388190bc13861033cb04f3 |
completed | May 12, 2026, 9:15 a.m. |
Created at: April 10, 2026, 10:12 a.m.