Triple
T16997316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Werburgh |
E412350
|
entity |
| Predicate | hasCultCentre |
P36126
|
FINISHED |
| Object | Hanbury |
E1245113
|
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: Hanbury | Statement: [Saint Werburgh, hasCultCentre, Hanbury]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hanbury Context triple: [Saint Werburgh, hasCultCentre, Hanbury]
-
A.
Hanbury
chosen
Hanbury is a historic English village known for its early medieval religious significance and association with the cult of Saint Werburgh.
-
B.
Horbury
Horbury is a town in West Yorkshire, England, historically part of the Wakefield area and known for its industrial heritage and parish church.
-
C.
Henbury
Henbury is a small settlement within the civil parish of Sturminster Marshall in Dorset, England.
-
D.
Hanborough
Hanborough is a civil parish in West Oxfordshire, England, encompassing the villages of Long Hanborough and Church Hanborough.
-
E.
Oldbury
Oldbury is a town in the West Midlands of England that serves as the administrative centre of the Metropolitan Borough of Sandwell.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d2885f888190ab1406f55a91bf93 |
completed | April 18, 2026, 6:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01233134288190bbe151f257150dfb |
completed | May 11, 2026, 12:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.