Triple
T15648954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belaugh |
E376253
|
entity |
| Predicate | hasWaterwayAccess |
P31589
|
FINISHED |
| Object | River Bure navigation |
—
|
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: River Bure navigation | Statement: [Belaugh, hasWaterwayAccess, River Bure navigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaterwayAccess Context triple: [Belaugh, hasWaterwayAccess, River Bure navigation]
-
A.
waterwayAccess
chosen
Indicates that one location has direct access to a waterway (such as a river, canal, or sea route) that can be used for transport, navigation, or related activities.
-
B.
hasWaterfrontAccessTo
Indicates that one entity is directly adjacent to and can physically access a particular body of water, such as a lake, river, or ocean.
-
C.
hasFishingAccess
Indicates that an entity is permitted or able to fish in or otherwise use a particular water body or fishing area.
-
D.
hasSeaAccess
Indicates that an entity has direct access to the sea, typically via a coastline, port, or navigable waterway connected to the sea.
-
E.
hasWaterChannel
Indicates that one entity possesses or contains a channel or conduit through which water flows or is transported.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ed7212c8190be6ff76afa25f7ca |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:15 a.m.