Triple
T19766087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knottingley and Goole Canal |
E474759
|
entity |
| Predicate | waterwayRegion |
P76490
|
FINISHED |
| Object | northern England |
—
|
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: northern England | Statement: [Knottingley and Goole Canal, waterwayRegion, northern England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterwayRegion Context triple: [Knottingley and Goole Canal, waterwayRegion, northern England]
-
A.
waterwaySystem
Indicates that one entity is part of, or belongs to, a connected network of waterways associated with another entity.
-
B.
watercourseThroughRegion
Indicates that a watercourse (such as a river or stream) passes through or traverses a specified region.
-
C.
waterbodyRegion
chosen
Indicates that a water body is located within, associated with, or spans a particular geographic region.
-
D.
waterwayServed
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
-
E.
primaryWaterways
Indicates that the related entities are connected through major or principal bodies of water, such as main rivers, canals, or shipping routes that serve as key waterways between them.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e653232e508190a7d484c0a1e2939a |
completed | April 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.