Triple
T485603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irlam Lock |
E9868
|
entity |
| Predicate | hasWaterwayRole |
P13535
|
FINISHED |
| Object | navigation control point |
—
|
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: navigation control point | Statement: [Irlam Lock, hasWaterwayRole, navigation control point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaterwayRole Context triple: [Irlam Lock, hasWaterwayRole, navigation control point]
-
A.
waterwayServed
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
-
B.
waterwaySystem
Indicates that one entity is part of, or belongs to, a connected network of waterways associated with another entity.
-
C.
mouthOfWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water or another watercourse.
-
D.
mouthOfTheWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water.
-
E.
connectsBodyOfWater
Indicates a relationship where one entity serves as a link or passage between two bodies of water, allowing them to be joined or interact.
- F. None of above. chosen
Provenance (4 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0bb46788190b40182bf2a54f98f |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf48ec08190b85d07e194f99c49 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeba8a488190986cc7381332f783 |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.