Triple
T6717212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Wissey |
E153301
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Hilborough |
E332491
|
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: Hilborough | Statement: [River Wissey, flowsThrough, Hilborough]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hilborough Context triple: [River Wissey, flowsThrough, Hilborough]
-
A.
Hilborough
chosen
Hilborough is a small village in Norfolk, England, known historically as the birthplace of Anglican clergyman Edmund Nelson, father of Admiral Horatio Nelson.
-
B.
Hanborough
Hanborough is a civil parish in West Oxfordshire, England, encompassing the villages of Long Hanborough and Church Hanborough.
-
C.
Horbury
Horbury is a town in West Yorkshire, England, historically part of the Wakefield area and known for its industrial heritage and parish church.
-
D.
Hadleigh
Hadleigh is a historic market town in Suffolk, England, known for its medieval buildings and traditional rural character.
-
E.
Hellingly
Hellingly is a village and civil parish in East Sussex, England, known for its rural character and historic parish church.
- 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_69c68809b4608190a2509ddb5ab87f05 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d12765a48190b485176dc2ffa0fa |
completed | March 27, 2026, 6:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c700993128819081614ccfa68d7320 |
completed | March 27, 2026, 10:11 p.m. |
Created at: March 27, 2026, 2:07 p.m.