Triple
T22735933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goring lock house |
E562270
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Goring 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: Goring Lock | Statement: [Goring lock house, locatedNear, Goring Lock]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Goring Lock Context triple: [Goring lock house, locatedNear, Goring Lock]
-
A.
Goring Lock
chosen
Goring Lock is a lock and weir on the River Thames in England, helping to manage river navigation and water levels near the village of Goring-on-Thames.
-
B.
Iffley Lock
Iffley Lock is a historic lock and weir on the River Thames near Oxford, England, known for its picturesque setting and traditional stone lock-keeper’s cottage.
-
C.
Teddington Lock
Teddington Lock is a major lock and weir complex on the River Thames in southwest London, marking the tidal limit of the river and serving as an important navigation and flood-control point.
-
D.
Cookham Lock
Cookham Lock is a lock and weir on the River Thames in Berkshire, England, serving river traffic near the village of Cookham.
-
E.
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.
- 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_69e24550859c81908727d91efc3a81b4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1796fc2a88190a4d86b421345b088 |
completed | April 29, 2026, 3:22 a.m. |
Created at: April 17, 2026, 3:22 p.m.