Triple
T25031088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | uranium-235 |
E626843
|
entity |
| Predicate | fissionProduces |
P158164
|
FINISHED |
| Object | fission fragments |
—
|
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: fission fragments | Statement: [uranium-235, fissionProduces, fission fragments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fissionProduces Context triple: [uranium-235, fissionProduces, fission fragments]
-
A.
typeOfIsotopesProduced
Indicates the kinds or categories of isotopes that are generated or produced by a given process, source, or entity.
-
B.
numberOfIsotopesProduced
Indicates the quantity of distinct isotopes that are generated or obtained from a specified process, reaction, or source.
-
C.
decayProduct
Indicates that one entity is the resulting product formed when another entity undergoes a decay process.
-
D.
fissileWith
Indicates that one material can undergo or sustain nuclear fission when interacting with another specified material or under conditions defined by that material.
-
E.
neutronCaptureProduct
Indicates the nuclide that results from a neutron capture reaction involving a given target nucleus.
- 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 18, 2026, 6:07 a.m.