Triple
T23369713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeya Hydroelectric Power Station |
E593427
|
entity |
| Predicate | hasReservoirType |
P34678
|
FINISHED |
| Object | artificial lake |
—
|
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: artificial lake | Statement: [Zeya Hydroelectric Power Station, hasReservoirType, artificial lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReservoirType Context triple: [Zeya Hydroelectric Power Station, hasReservoirType, artificial lake]
-
A.
isReservoir
Indicates that one entity functions as a storage or holding container (often for fluids or resources) for another entity.
-
B.
reservoirType
chosen
Indicates the specific kind or classification of a reservoir associated with an entity.
-
C.
includesReservoir
Indicates that one entity contains or encompasses a reservoir as part of its structure, system, or area.
-
D.
usesReservoir
Indicates that one entity draws upon, depends on, or operates using a particular reservoir as a resource or source.
-
E.
isReservoirOn
Indicates that a reservoir is physically located on or situated atop another specified entity or structure.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0aff84c8190a5a6bf52adae1c9a |
completed | April 29, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:32 p.m.