Triple
T37140996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lea Valley aqueducts |
E920107
|
entity |
| Predicate | usesChannelType |
P116567
|
FINISHED |
| Object | open channels |
—
|
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: open channels | Statement: [Lea Valley aqueducts, usesChannelType, open channels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesChannelType Context triple: [Lea Valley aqueducts, usesChannelType, open channels]
-
A.
includesChannelType
chosen
Indicates that one entity encompasses or supports a specified type of communication or distribution channel as part of its structure or functionality.
-
B.
basedOnChannel
Indicates that something is determined, derived, or decided according to a particular channel as its basis or reference.
-
C.
canChannel
Indicates that one entity is able to direct, transmit, or route something (such as information, energy, or resources) through another entity or medium.
-
D.
ownedChannel
Indicates that one entity possesses ownership or control over a particular channel.
-
E.
supportsChannels
Indicates that one entity is capable of handling, providing, or being compatible with one or more specified channels for communication, distribution, or operation.
- 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_69f76e9e9d008190a250b0387c992c74 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: May 3, 2026, 4:15 p.m.