Triple
T15522105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nitrogen-15 |
E368992
|
entity |
| Predicate | betaDecay |
P5370
|
FINISHED |
| Object | not observed |
—
|
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: not observed | Statement: [nitrogen-15, betaDecay, not observed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: betaDecay Context triple: [nitrogen-15, betaDecay, not observed]
-
A.
betaDecayInvolves
Indicates that a beta decay process includes or is characterized by the participation of a specified particle, product, or sub-process.
-
B.
radioactivity
Indicates that an entity emits ionizing radiation due to unstable atomic nuclei undergoing radioactive decay.
-
C.
decayWidth
Indicates the total probability per unit time (or corresponding energy measure) that an unstable particle will decay via all possible channels.
-
D.
decayMode
chosen
Indicates the specific process or pathway by which an unstable entity transforms or decays into other products.
-
E.
hasNoStableIsotopes
Indicates that the specified chemical element lacks any isotopes that are stable and all of its isotopes are radioactive.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0403543188190abac49d2b9decb89 |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded28ab0588190a47a9090d1238707 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 4:04 a.m.