Triple
T28016428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian nuclear power program |
E707555
|
entity |
| Predicate | developsReactorDesign |
P95412
|
FINISHED |
| Object | VVER-1000 |
—
|
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: VVER-1000 | Statement: [Russian nuclear power program, developsReactorDesign, VVER-1000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developsReactorDesign Context triple: [Russian nuclear power program, developsReactorDesign, VVER-1000]
-
A.
reactorDesignGeneration
Indicates the generation or iteration level of a reactor’s design within a sequence of reactor design developments.
-
B.
reactorDesigner
chosen
Indicates that an entity is responsible for designing or having designed a reactor.
-
C.
combustionChamberDesign
Indicates the specific configuration and structural characteristics of a combustion chamber that determine how fuel and oxidizer mix, ignite, and burn within an engine or reactor.
-
D.
engineeringDesign
Indicates the relationship in which an entity is responsible for planning, specifying, or creating the technical design of another entity (such as a system, component, or structure).
-
E.
reactorType
Indicates the specific kind or category of reactor associated with an entity.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 27, 2026, 8:07 p.m.