Triple
T32886840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | community of Mount Storm, West Virginia |
E841222
|
entity |
| Predicate | lakeUsedFor |
P44236
|
FINISHED |
| Object | cooling water for power generation |
—
|
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 for power generation | Statement: [community of Mount Storm, West Virginia, lakeUsedFor, cooling water for power generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lakeUsedFor Context triple: [community of Mount Storm, West Virginia, lakeUsedFor, cooling water for power generation]
-
A.
waterbodyUsedFor
chosen
Indicates that a particular water body is utilized for a specific purpose, activity, or function.
-
B.
reservoirUse
Indicates the way a reservoir is utilized or the purpose for which its stored water is used.
-
C.
usesLakeFor
Indicates that an entity utilizes a lake as a resource or setting for some purpose, activity, or function.
-
D.
basinUse
Indicates that a basin is used for a particular purpose, activity, or function.
-
E.
lakeCreationPurpose
Indicates the intended purpose or primary function for which a lake was created or established.
- 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_69f349446e288190a70c05bcc4d81172 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:18 a.m.