Triple
T28016246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalinin-1 |
E707551
|
entity |
| Predicate | thermalNeutronSpectrum |
P11819
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kalinin-1, thermalNeutronSpectrum, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thermalNeutronSpectrum Context triple: [Kalinin-1, thermalNeutronSpectrum, true]
-
A.
neutronSpectrum
chosen
Indicates the energy distribution or range of neutrons present in a given system, interaction, or environment.
-
B.
thermalNeutronReactor
Indicates that the subject is a nuclear reactor that operates using thermal (low-energy) neutrons to sustain its fission chain reaction.
-
C.
thermalNeutronCaptureCrossSection
Indicates the probability that a nucleus will capture a thermal (low-energy) neutron, expressed as an effective interaction cross-sectional area.
-
D.
neutronEmissionRate
Indicates the rate at which neutrons are emitted from a source or system over a given period of time.
-
E.
thermalNeutronModerator
Indicates a relationship where one entity serves to slow down or moderate thermal neutrons interacting with another 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_69f63c0796288190a5936b67d90abd00 |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:07 p.m.