Triple
T4224232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Lee |
E94414
|
entity |
| Predicate | hasFeature |
P182
|
FINISHED |
| Object | Bow Locks |
E259373
|
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: Bow Locks | Statement: [River Lee, hasFeature, Bow Locks]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bow Locks Context triple: [River Lee, hasFeature, Bow Locks]
-
A.
Bow Locks
chosen
Bow Locks is a set of navigation locks on the River Lea in East London that control water levels and enable boat passage between the river and surrounding waterways.
-
B.
Soo Locks
The Soo Locks are a set of ship locks on the St. Marys River between Lake Superior and Lake Huron that enable vessels to bypass the river’s rapids and navigate the Great Lakes.
-
C.
Dutton Locks
Dutton Locks is a set of navigation locks on the River Weaver in Cheshire, England, used to manage water levels and enable boat passage along the river.
-
D.
Kembs lock
Kembs lock is a major navigation lock on the Grand Canal d’Alsace in eastern France, facilitating ship passage along the Rhine.
-
E.
Nickajack Lock
Nickajack Lock is a navigation lock on the Tennessee River in Tennessee that helps manage river traffic and water levels as part of the Tennessee Valley Authority system.
- 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_69b3453700a08190ae88792e3dc63207 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e4bf6088190926b982039a12079 |
completed | March 12, 2026, 11:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5964532e08190bb1dc56f734e6ebb |
completed | March 14, 2026, 5:09 p.m. |
Created at: March 12, 2026, 11:04 p.m.