Triple
T23236289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caerwys |
E581305
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Holywell |
—
|
NE NERFINISHED |
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: Holywell | Statement: [Caerwys, locatedNear, Holywell]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Holywell Context triple: [Caerwys, locatedNear, Holywell]
-
A.
Holywell
chosen
Holywell is a historic market town in northeast Wales renowned for St Winefride's Well, a major medieval pilgrimage site often called the "Lourdes of Wales."
-
B.
Holywell
Holywell is a village in the Metropolitan Borough of North Tyneside in Tyne and Wear, England.
-
C.
Holwell
Holwell is a small rural village located within the North Hertfordshire district of Hertfordshire, England.
-
D.
Bywell
Bywell is a small historic village in Northumberland, England, situated on the north bank of the River Tyne and known for its medieval churches and castle ruins.
-
E.
Banwell
Banwell is a village and civil parish in North Somerset, England, known for its historic caves and medieval architecture.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2460556f88190be1744a84a84173f |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f192e98dec8190a23385600bed9ae0 |
completed | April 29, 2026, 5:11 a.m. |
Created at: April 17, 2026, 4:09 p.m.