Triple
T16203415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | californium-252 |
E393260
|
entity |
| Predicate | significantDecayMode |
P5370
|
FINISHED |
| Object | spontaneous fission |
—
|
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: spontaneous fission | Statement: [californium-252, significantDecayMode, spontaneous fission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantDecayMode Context triple: [californium-252, significantDecayMode, spontaneous fission]
-
A.
decayMode
chosen
Indicates the specific process or pathway by which an unstable entity transforms or decays into other products.
-
B.
decayProduct
Indicates that one entity is the resulting product formed when another entity undergoes a decay process.
-
C.
decayWidth
Indicates the total probability per unit time (or corresponding energy measure) that an unstable particle will decay via all possible channels.
-
D.
primaryDecayChannelStudied
Indicates that the primary mode of decay for a particle or system is the main subject of investigation or analysis.
-
E.
betaDecayInvolves
Indicates that a beta decay process includes or is characterized by the participation of a specified particle, product, or sub-process.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2270ca18c8190a259992aed4ec072 |
completed | April 17, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.