Triple
T4383980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advanced Test Reactor |
E99195
|
entity |
| Predicate | neutronFlux |
P52330
|
FINISHED |
| Object | high-flux |
—
|
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: high-flux | Statement: [Advanced Test Reactor, neutronFlux, high-flux]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neutronFlux Context triple: [Advanced Test Reactor, neutronFlux, high-flux]
-
A.
neutronFluxType
chosen
Indicates the specific classification or category of neutron flux characterizing how neutrons are distributed or behave in a given context.
-
B.
neutronSpectrum
Indicates the energy distribution or range of neutrons present in a given system, interaction, or environment.
-
C.
thermalNeutronCaptureCrossSection
Indicates the probability that a nucleus will capture a thermal (low-energy) neutron, expressed as an effective interaction cross-sectional area.
-
D.
hasNeutronNumber
Indicates that an entity (typically an atom or nuclide) has a specified number of neutrons in its nucleus.
-
E.
numberOfIsotopesProduced
Indicates the quantity of distinct isotopes that are generated or obtained from a specified process, reaction, or source.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35263970c8190904ee20d81715833 |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f557fe8819085032bf7f0cea5dc |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:18 p.m.