Triple
T36580858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capel Celyn |
E902390
|
entity |
| Predicate | purposeOfReservoir |
P40334
|
FINISHED |
| Object | water supply for Liverpool |
—
|
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 Liverpool | Statement: [Capel Celyn, purposeOfReservoir, water supply for Liverpool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfReservoir Context triple: [Capel Celyn, purposeOfReservoir, water supply for Liverpool]
-
A.
reservoirUse
chosen
Indicates the way a reservoir is utilized or the purpose for which its stored water is used.
-
B.
reservoirType
Indicates the specific kind or classification of a reservoir associated with an entity.
-
C.
reservoirRole
Indicates that an entity functions as a storage or holding medium for another entity, such as accumulating, containing, or buffering it for later use or release.
-
D.
reservoir
Indicates that one entity serves as a storage or containment source (often for a resource) that can supply or affect another entity.
-
E.
reservoirAlsoKnownAs
Indicates that a reservoir is referred to by an alternative name or alias.
- 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_69f76e64d8908190868473959a250b94 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.