Triple
T4383909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | einsteinium |
E99193
|
entity |
| Predicate | radioactiveHazard |
P37366
|
FINISHED |
| Object | alpha emitter |
—
|
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: alpha emitter | Statement: [einsteinium, radioactiveHazard, alpha emitter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radioactiveHazard Context triple: [einsteinium, radioactiveHazard, alpha emitter]
-
A.
isHighlyRadioactive
Indicates that the subject emits ionizing radiation at a very high level relative to typical or safe standards.
-
B.
radioactivity
chosen
Indicates that an entity emits ionizing radiation due to unstable atomic nuclei undergoing radioactive decay.
-
C.
radioisotopesReleased
Indicates that radioactive isotopes are emitted or discharged from a source into the surrounding environment.
-
D.
usedRadioisotope
Indicates that one entity employed or applied a specific radioisotope in an action, process, or context involving another entity.
-
E.
hasNotableHazard
Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35263970c8190904ee20d81715833 |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f557fe8819085032bf7f0cea5dc |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:18 p.m.