Triple
T19706693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iffley Lock |
E473233
|
entity |
| Predicate | downstreamFrom |
P5956
|
FINISHED |
| Object | Osney Lock |
—
|
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: Osney Lock | Statement: [Iffley Lock, downstreamFrom, Osney Lock]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Osney Lock Context triple: [Iffley Lock, downstreamFrom, Osney Lock]
-
A.
Osney Lock
chosen
Osney Lock is a lock on the River Thames in Oxford, England, used to manage river navigation and water levels near the city.
-
B.
Cookham Lock
Cookham Lock is a lock and weir on the River Thames in Berkshire, England, serving river traffic near the village of Cookham.
-
C.
Nuneham Lock
Nuneham Lock is a lock on the River Thames in Oxfordshire, England, serving river traffic near the village of Nuneham Courtenay.
-
D.
Pyrford Lock
Pyrford Lock is a historic lock on the River Wey Navigation in Surrey, England, used to manage water levels and enable boat passage along the waterway.
-
E.
Radcot Lock
Radcot Lock is a lock on the River Thames in Oxfordshire, England, used to manage river navigation and water levels near the village of Radcot.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642bb5cd4819090e4c62bd74c4324 |
completed | April 20, 2026, 3:14 p.m. |
Created at: April 10, 2026, 1:46 p.m.