Triple
T29992483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | helium-4 |
E761917
|
entity |
| Predicate | dominantIsotopeOf |
P19724
|
FINISHED |
| Object | helium |
—
|
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: helium | Statement: [helium-4, dominantIsotopeOf, helium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantIsotopeOf Context triple: [helium-4, dominantIsotopeOf, helium]
-
A.
mostAbundantIsotope
chosen
Indicates that one isotope of an element is identified as the most frequently occurring (highest natural abundance) among all its isotopes.
-
B.
mostStableIsotope
Indicates that the linked isotope is the most stable (i.e., least likely to undergo radioactive decay) among all isotopes of the referenced element.
-
C.
isLighterIsotopeOf
Indicates that one isotope has a lower atomic mass (fewer neutrons) than another isotope of the same element.
-
D.
intendedIsotope
Indicates that one entity is the specific isotope that another entity is meant or designed to refer to, use, or produce.
-
E.
naturalIsotope
Indicates that one entity is a naturally occurring isotope form of another element or nuclide.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 29, 2026, 6:39 p.m.