Triple
T4383900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | einsteinium |
E99193
|
entity |
| Predicate | otherIsotope |
P19723
|
FINISHED |
| Object | einsteinium-253 |
—
|
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: einsteinium-253 | Statement: [einsteinium, otherIsotope, einsteinium-253]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: otherIsotope Context triple: [einsteinium, otherIsotope, einsteinium-253]
-
A.
commonIsotope
Indicates that two substances share the same most naturally abundant isotope of an element.
-
B.
isotopes
chosen
Indicates that two or more atomic nuclei are variants of the same chemical element that differ in neutron number (and thus mass number) but share the same number of protons.
-
C.
isTransuranic
Indicates that an element has an atomic number greater than that of uranium, placing it beyond uranium in the periodic table.
-
D.
usedRadioisotope
Indicates that one entity employed or applied a specific radioisotope in an action, process, or context involving another entity.
-
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_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.