Triple
T27942874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Storm Power Station |
E700798
|
entity |
| Predicate | lakeCreatedFor |
P154318
|
FINISHED |
| Object | cooling water supply |
—
|
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: cooling water supply | Statement: [Mount Storm Power Station, lakeCreatedFor, cooling water supply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lakeCreatedFor Context triple: [Mount Storm Power Station, lakeCreatedFor, cooling water supply]
-
A.
lakeCreationPurpose
chosen
Indicates the intended purpose or primary function for which a lake was created or established.
-
B.
createsLake
Indicates that one entity causes the formation or existence of a lake in relation to another entity or location.
-
C.
lakeOrigin
Indicates that a lake originates from, is formed by, or has its source in a specified geographic or hydrological feature.
-
D.
waterBodyCreated
Indicates that one entity is responsible for the formation or creation of a particular body of water.
-
E.
lakeAlternateName
Indicates that a lake is known by an alternative or additional name.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:19 p.m.