Triple
T2393952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mendelevium |
E47604
|
entity |
| Predicate | isotopesCountKnown |
P37376
|
FINISHED |
| Object | more than 15 isotopes |
—
|
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: more than 15 isotopes | Statement: [mendelevium, isotopesCountKnown, more than 15 isotopes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isotopesCountKnown Context triple: [mendelevium, isotopesCountKnown, more than 15 isotopes]
-
A.
isotopesCountObserved
chosen
Indicates the number of distinct isotopes of an element that have been experimentally observed or detected.
-
B.
numberOfIsotopesProduced
Indicates the quantity of distinct isotopes that are generated or obtained from a specified process, reaction, or source.
-
C.
isotopes
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.
-
D.
commonIsotope
Indicates that two substances share the same most naturally abundant isotope of an element.
-
E.
isNucleusOfIsotope
Indicates that a given nucleus belongs to and characterizes a specific isotope.
- 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_69a88a1c450c81909f61abb8b6863885 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc87827d88190bb2351a688e6de32 |
completed | March 7, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69abc5a1b5748190b4cd8989700f4dd2 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.