Triple
T19045693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Rood Church |
E466124
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Holybourne |
—
|
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: Holybourne | Statement: [Holy Rood Church, locatedIn, Holybourne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Holybourne Context triple: [Holy Rood Church, locatedIn, Holybourne]
-
A.
Holybourne
chosen
Holybourne is a small village in Hampshire, England, situated just outside the market town of Alton.
-
B.
Southbourne
Southbourne is a village and civil parish in West Sussex, England, situated near Chichester on the south coast.
-
C.
Southbourne
Southbourne is a coastal suburb in the Bournemouth area of Dorset, England, known for its sandy beaches and residential character.
-
D.
Oldbourne
Oldbourne is an alternative historical spelling of "Old Bourne," typically referring to an old stream or settlement whose name incorporates the term "bourne" for a small river.
-
E.
Forbury Hill
Forbury Hill is a historic earthwork mound in Reading, England, forming part of the Forbury Gardens near the ruins of Reading Abbey and long associated with medieval defensive and ceremonial uses.
- 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d80466f88190988171920f2be7dc |
completed | April 20, 2026, 7:38 a.m. |
Created at: April 10, 2026, 12:03 p.m.