Triple
T4409715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hollingworth Lake Country Park |
E94822
|
entity |
| Predicate | originalUseOfReservoir |
P40334
|
FINISHED |
| Object | water supply for Rochdale Canal |
—
|
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: water supply for Rochdale Canal | Statement: [Hollingworth Lake Country Park, originalUseOfReservoir, water supply for Rochdale Canal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalUseOfReservoir Context triple: [Hollingworth Lake Country Park, originalUseOfReservoir, water supply for Rochdale Canal]
-
A.
reservoirUse
chosen
Indicates the way a reservoir is utilized or the purpose for which its stored water is used.
-
B.
reservoir
Indicates that one entity serves as a storage or containment source (often for a resource) that can supply or affect another entity.
-
C.
reservoirCreated
Indicates that a reservoir has been brought into existence, typically through construction or formation by some agent or process.
-
D.
reservoirAlsoKnownAs
Indicates that a reservoir is referred to by an alternative name or alias.
-
E.
reservoirType
Indicates the specific kind or classification of a reservoir associated with an entity.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3548e24d08190a38c0bcd4b6ad571 |
completed | March 13, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69b34f5b36a881909bf2e970aa523390 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:28 p.m.