Triple
T29992504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | helium-4 |
E761917
|
entity |
| Predicate | neutronSeparationEnergy |
P168333
|
FINISHED |
| Object | high |
—
|
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 | Statement: [helium-4, neutronSeparationEnergy, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neutronSeparationEnergy Context triple: [helium-4, neutronSeparationEnergy, high]
-
A.
spontaneousFissionBranchingRatio
Indicates the proportion of a nuclide’s decays that proceed via spontaneous fission compared to all its possible decay modes.
-
B.
averageNeutronsPerFission
Indicates the typical number of neutrons released as a result of a single nuclear fission event.
-
C.
hasNeutronNumber
Indicates that an entity (typically an atom or nuclide) has a specified number of neutrons in its nucleus.
-
D.
thermalNeutronCaptureCrossSection
Indicates the probability that a nucleus will capture a thermal (low-energy) neutron, expressed as an effective interaction cross-sectional area.
-
E.
neutronEmissionRate
Indicates the rate at which neutrons are emitted from a source or system over a given period of time.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6791b73a081908c15d046673bbc37 |
completed | May 2, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:39 p.m.