Triple
T11921043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mid Worcestershire |
E283654
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Pershore |
E185391
|
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: Pershore | Statement: [Mid Worcestershire, hasTown, Pershore]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pershore Context triple: [Mid Worcestershire, hasTown, Pershore]
-
A.
Pershore
chosen
Pershore is a historic market town on the River Avon in Worcestershire, England, known for its Georgian architecture and annual plum festival.
-
B.
Bridgnorth
Bridgnorth is a historic market town in Shropshire, England, known for its dramatic position on the River Severn and its high and low town layout linked by a funicular railway.
-
C.
Sherborne
Sherborne is a historic market town in southwest England renowned for its medieval abbey, castles, and well-preserved architecture.
-
D.
Sherborne
Sherborne is a small rural village in West Oxfordshire, England, known for its traditional Cotswold stone buildings and picturesque countryside setting.
-
E.
Hednesford
Hednesford is a small town in Staffordshire, England, situated near Cannock Chase and known historically for its coal mining heritage.
- 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_69d8e8e1b08481909ed291667035f330 |
completed | April 10, 2026, 12:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f45891f9c081909250a0aa0f7448d2 |
completed | May 1, 2026, 7:38 a.m. |
Created at: April 8, 2026, 9:45 p.m.