Triple
T28286633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalinin-3 |
E713297
|
entity |
| Predicate | reactorCoolantLoops |
P90828
|
FINISHED |
| Object | four-loop configuration |
—
|
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: four-loop configuration | Statement: [Kalinin-3, reactorCoolantLoops, four-loop configuration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactorCoolantLoops Context triple: [Kalinin-3, reactorCoolantLoops, four-loop configuration]
-
A.
hasReactorCoolantSystem
chosen
Indicates that an entity is equipped with or includes a reactor coolant system used to remove heat from a reactor.
-
B.
nrcReactorUnitNumber
Indicates the specific unit number assigned to a nuclear reactor within an NRC-licensed facility.
-
C.
numberOfReactors
Indicates the quantity of reactors associated with or contained by a given entity.
-
D.
reactorVesselPressure
Indicates the pressure exerted by the contents within a reactor vessel during its operation.
-
E.
thermalNeutronReactor
Indicates that the subject is a nuclear reactor that operates using thermal (low-energy) neutrons to sustain its fission chain reaction.
- 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 11:26 p.m.