Triple
T12292018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hay-on-Wye |
E292986
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | HEREFORD |
E65056
|
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: HEREFORD | Statement: [Hay-on-Wye, hasPostTown, HEREFORD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HEREFORD Context triple: [Hay-on-Wye, hasPostTown, HEREFORD]
-
A.
Hereford
chosen
Hereford is a cathedral city in Herefordshire, England, known for its historic architecture and role as a military and agricultural center.
-
B.
Hereford
Hereford is a small city in the Texas Panhandle known for its strong agricultural and cattle industry.
-
C.
Bideford
Bideford is a historic port town on the River Torridge in North Devon, England, known for its maritime heritage and role as a local commercial center.
-
D.
Bury St Edmunds
Bury St Edmunds is a historic market town in Suffolk, England, known for its ruined abbey, cathedral, and association with the medieval martyr King Edmund.
-
E.
Shrewsbury
Shrewsbury is a historic market town in Shropshire, England, known for its well-preserved medieval streets and timber-framed buildings.
- 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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d22ba488190914342fa7e69e159 |
completed | April 10, 2026, 3:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e775dac819099d44b61cbccc109 |
completed | May 2, 2026, 3:55 p.m. |
Created at: April 8, 2026, 9:52 p.m.