Triple
T23336201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Зея |
E591591
|
entity |
| Predicate | водохранилище |
P11309
|
FINISHED |
| Object | Зейское водохранилище |
—
|
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: Зейское водохранилище | Statement: [Зея, водохранилище, Зейское водохранилище]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: водохранилище Context triple: [Зея, водохранилище, Зейское водохранилище]
-
A.
reservoir
chosen
Indicates that one entity serves as a storage or containment source (often for a resource) that can supply or affect another entity.
-
B.
riverImpounded
Indicates that a river’s natural flow is obstructed or controlled, typically by a dam or similar structure, creating an impoundment such as a reservoir.
-
C.
downstreamReservoir
Indicates that one reservoir is located downstream of, and receives water flow from, another reservoir in a connected water system.
-
D.
reservoirType
Indicates the specific kind or classification of a reservoir associated with an entity.
-
E.
reservoirGrossStorageCapacity_m3
Indicates the total volume of water a reservoir can hold when filled to its maximum designed storage level, measured in cubic meters.
- 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_69e25d20156c81908c5c53195bd9c738 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197f1e0588190bf073b92be0bf9e4 |
completed | April 29, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:16 p.m.