Triple
T23369005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marlow Lock |
E593409
|
entity |
| Predicate | upstreamFrom |
P5955
|
FINISHED |
| Object | Cookham 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: Cookham Lock | Statement: [Marlow Lock, upstreamFrom, Cookham Lock]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cookham Lock Context triple: [Marlow Lock, upstreamFrom, Cookham Lock]
-
A.
Cookham Lock
chosen
Cookham Lock is a lock and weir on the River Thames in Berkshire, England, serving river traffic near the village of Cookham.
-
B.
Shepperton Lock
Shepperton Lock is a lock on the River Thames in England, used to manage river navigation and water levels near the town of Shepperton.
-
C.
Hanham Lock
Hanham Lock is a lock on the River Avon in South Gloucestershire, England, known for managing river navigation and marking the tidal limit of the waterway near Hanham.
-
D.
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.
-
E.
Eynsham Lock
Eynsham Lock is a lock on the River Thames in Oxfordshire, England, used to manage river navigation and water levels near the village of Eynsham.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0aed374819097d38f51894bee44 |
completed | April 29, 2026, 6:09 a.m. |
Created at: April 17, 2026, 5:32 p.m.