Triple
T28016265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalinin-1 |
E707551
|
entity |
| Predicate | reactorTechnologyClass |
P3675
|
FINISHED |
| Object | pressurized water reactor |
—
|
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: pressurized water reactor | Statement: [Kalinin-1, reactorTechnologyClass, pressurized water reactor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactorTechnologyClass Context triple: [Kalinin-1, reactorTechnologyClass, pressurized water reactor]
-
A.
reactorTechnologySupplier
Indicates that one entity supplies or provides reactor technology to another entity.
-
B.
reactorType
chosen
Indicates the specific kind or category of reactor associated with an entity.
-
C.
thermalNeutronReactor
Indicates that the subject is a nuclear reactor that operates using thermal (low-energy) neutrons to sustain its fission chain reaction.
-
D.
electricalCapacityPerReactor_MWe
Indicates the electrical power output capacity, measured in megawatts electric (MWe), that is provided by each individual reactor.
-
E.
fuelAssemblyType
Indicates the specific design or classification of a fuel assembly 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_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 8:07 p.m.