Triple
T18383302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hodder Bridge |
E446510
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | River Hodder |
—
|
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: River Hodder | Statement: [Hodder Bridge, namedAfter, River Hodder]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: River Hodder Context triple: [Hodder Bridge, namedAfter, River Hodder]
-
A.
River Hodder
chosen
River Hodder is a river in Lancashire, England, known for flowing through the Forest of Bowland and joining the River Ribble near Great Mitton.
-
B.
Ager River
The Ager River is a watercourse in Upper Austria that flows through the Salzkammergut region and ultimately joins the Traun River.
-
C.
River Brent
The River Brent is a tributary of the River Thames in West London, flowing through several London boroughs and giving its name to the London Borough of Brent.
-
D.
River Brun
River Brun is a small river in Lancashire, England, that flows through the town of Burnley and contributes to its local landscape and waterways.
-
E.
Lez River
The Lez River is a short coastal river in southern France that flows through the city of Montpellier before emptying into the Mediterranean Sea.
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e5179c931c8190b1c7c8284f42f7b7 |
completed | April 19, 2026, 5:57 p.m. |
Created at: April 10, 2026, 10:45 a.m.