Triple
T24778328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krasnoyarsk Reservoir |
E619921
|
entity |
| Predicate | formedByStructure |
P972
|
FINISHED |
| Object | Krasnoyarsk Dam |
—
|
NE NERFINISHED |
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: Krasnoyarsk Dam | Statement: [Krasnoyarsk Reservoir, formedByStructure, Krasnoyarsk Dam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedByStructure Context triple: [Krasnoyarsk Reservoir, formedByStructure, Krasnoyarsk Dam]
-
A.
formedBy
chosen
Indicates that something comes into existence or is created as a result of a specific agent, process, or combination of components.
-
B.
formedByParty
Indicates that something (such as an organization, group, or entity) has been created, established, or constituted by a specific party.
-
C.
containsStructureFrom
Indicates that one entity includes or incorporates a structural component originating from another entity.
-
D.
linkedByStructure
Indicates that two entities are connected or associated through a shared structural element, configuration, or framework.
-
E.
hadStructure
Indicates that an entity possessed or was composed of a particular structural form, configuration, or physical arrangement.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 18, 2026, 4:41 a.m.