Triple
T28163338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalinin-4 |
E714953
|
entity |
| Predicate | hasReactorDesignFamily |
P171735
|
FINISHED |
| Object | VVER |
—
|
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 | Statement: [Kalinin-4, hasReactorDesignFamily, VVER]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReactorDesignFamily Context triple: [Kalinin-4, hasReactorDesignFamily, VVER]
-
A.
reactorFamily
Indicates that one reactor belongs to the same defined family or type grouping as another reactor, based on shared design or classification characteristics.
-
B.
designedByFamilyOf
Indicates that something was created, planned, or conceived by one or more members of a particular family or familial group.
-
C.
hasReactorUnit
Indicates that one entity possesses, contains, or is equipped with a specific reactor unit as a component or subsystem.
-
D.
reactorType
Indicates the specific kind or category of reactor associated with an entity.
-
E.
hasNuclearReactorType
chosen
Indicates that an entity possesses or is equipped with a specific type or classification of nuclear reactor.
- 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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
Created at: April 27, 2026, 10:07 p.m.