Triple
T16492960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | fermium-252 |
E400609
|
entity |
| Predicate | hasSecondaryDecayMode |
P123748
|
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: [fermium-252, hasSecondaryDecayMode, spontaneous fission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryDecayMode Context triple: [fermium-252, hasSecondaryDecayMode, spontaneous fission]
-
A.
hasSecondary
Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
-
B.
hasSecondaryBase
Indicates that an entity possesses or is associated with a secondary or additional base, distinct from its primary base.
-
C.
hasSecondaryFlavor
Indicates that an entity possesses an additional, subordinate flavor characteristic beyond its primary flavor.
-
D.
hasSecondaryCore
Indicates that an entity possesses an additional, subordinate core component alongside its primary core.
-
E.
hasSecondaryUsage
Indicates that an entity is associated with an additional, non-primary function or purpose beyond its main intended use.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e30cb648190a52cb32896c4ac5a |
completed | April 18, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:13 a.m.