Triple
T3840673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Flux Isotope Reactor |
E93441
|
entity |
| Predicate | neutronFluxType |
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: [High Flux Isotope Reactor, neutronFluxType, high flux]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neutronFluxType Context triple: [High Flux Isotope Reactor, neutronFluxType, high flux]
-
A.
neutronSpectrum
Indicates the energy distribution or range of neutrons present in a given system, interaction, or environment.
-
B.
reactorType
Indicates the specific kind or category of reactor associated with an entity.
-
C.
thermalNeutronCaptureCrossSection
Indicates the probability that a nucleus will capture a thermal (low-energy) neutron, expressed as an effective interaction cross-sectional area.
-
D.
neutrinoFlavorAtSource
Indicates the specific neutrino flavor (e.g., electron, muon, tau) that a neutrino possesses at its point of origin or production.
-
E.
neutrinoBeamDestination
Indicates the target location or object toward which a neutrino beam is directed or intended to travel.
- F. None of above. chosen
Provenance (4 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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeeba1535c8190b36e2ab2d4514b54 |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74dcecc819098285483ec721b40 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeeb828fb08190901d51edbe8bd304 |
completed | March 9, 2026, 3:47 p.m. |
Created at: March 9, 2026, 3:18 p.m.