Triple
T23369007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marlow Lock |
E593409
|
entity |
| Predicate | onReach |
P26816
|
FINISHED |
| Object | reach between Hurley Lock and Cookham Lock |
—
|
LITERAL 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: reach between Hurley Lock and Cookham Lock | Statement: [Marlow Lock, onReach, reach between Hurley Lock and Cookham Lock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onReach Context triple: [Marlow Lock, onReach, reach between Hurley Lock and Cookham Lock]
-
A.
reaches
chosen
Indicates that one entity extends or moves until it makes contact with, attains, or arrives at another entity or point.
-
B.
hasReach
Indicates that one entity is able to extend its influence, access, or physical span to another entity or area.
-
C.
canReach
Indicates that one entity is able to access, arrive at, or establish a path to another entity.
-
D.
hasLongerReachThan
Indicates that one entity can extend, influence, or physically reach farther than another entity.
-
E.
supportsReach
Indicates that one entity enables, facilitates, or maintains the ability of another entity to extend its influence, access, or coverage to additional targets or areas.
- F. None of above.
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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0aed374819097d38f51894bee44 |
completed | April 29, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:32 p.m.