Triple
T7598384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foulridge Tunnel |
E179916
|
entity |
| Predicate | locatedInWaterwaySystem |
P63896
|
FINISHED |
| Object | British canal network |
—
|
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: British canal network | Statement: [Foulridge Tunnel, locatedInWaterwaySystem, British canal network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInWaterwaySystem Context triple: [Foulridge Tunnel, locatedInWaterwaySystem, British canal network]
-
A.
isInWaterwaySystem
chosen
Indicates that an entity is part of, contained within, or traverses a particular waterway network or system.
-
B.
locatedOnWaterbody
Indicates that an entity is situated on or directly adjacent to a specified body of water.
-
C.
partOfWaterway
Indicates that one water-related feature is a constituent or segment of a larger waterway system.
-
D.
locatedInWaterBodyType
Indicates that an entity is situated within or on a body of water of a specified type (e.g., lake, river, ocean).
-
E.
associatedWithWaterways
Indicates a relationship in which something is connected, linked, or relevant to waterways such as rivers, canals, or streams.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9d67cf88190a3202c07f7cea7df |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:53 p.m.