Triple
T6423352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marlow |
E127996
|
entity |
| Predicate | hasRiverFeature |
P1094
|
FINISHED |
| Object | Marlow Lock |
E593409
|
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: Marlow Lock | Statement: [Marlow, hasRiverFeature, Marlow Lock]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Marlow Lock Context triple: [Marlow, hasRiverFeature, Marlow Lock]
-
A.
Marlow Lock
chosen
Marlow Lock is a historic lock on the River Thames in England, known for serving river traffic near the town of Marlow and contributing to the area's scenic riverside character.
-
B.
Molesey Lock
Molesey Lock is a lock on the River Thames in England, situated near East Molesey and used to manage river navigation and water levels.
-
C.
Gladstone Lock
Gladstone Lock is a major ship lock within the Port of Liverpool that enables large vessels to access the port’s dock system from the River Mersey.
-
D.
Thorne Lock
Thorne Lock is a canal lock on the Sheffield and South Yorkshire Navigation in South Yorkshire, England, used to raise and lower boats between different water levels.
-
E.
Allington Lock
Allington Lock is a key navigation and flood-control lock on the River Medway in Kent, England, marking the tidal limit of the river.
- 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_69c00838de888190af2eec0b80495efa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c06906eea88190a445c1ff1169c2b1 |
completed | March 22, 2026, 10:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6538a8e9c81909c406235117e0c87 |
completed | March 27, 2026, 9:53 a.m. |
Created at: March 22, 2026, 4:43 p.m.