Triple
T25031114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | uranium-235 |
E626843
|
entity |
| Predicate | yearOfIsotopeIdentification |
P161435
|
FINISHED |
| Object | 1935 |
—
|
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: 1935 | Statement: [uranium-235, yearOfIsotopeIdentification, 1935]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfIsotopeIdentification Context triple: [uranium-235, yearOfIsotopeIdentification, 1935]
-
A.
radioactiveIsotope
Indicates that one entity is a radioactive isotope of another, meaning it is an unstable nuclide of the same element that undergoes radioactive decay.
-
B.
commonIsotope
Indicates that two substances share the same most naturally abundant isotope of an element.
-
C.
yearObserved
Indicates the specific calendar year during which the referenced event, condition, or measurement was observed or recorded.
-
D.
intendedIsotope
Indicates that one entity is the specific isotope that another entity is meant or designed to refer to, use, or produce.
-
E.
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.
- 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_69f613bc641c819084343cc78d080640 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f613502d808190b89927e5e734b43a |
completed | May 2, 2026, 3:08 p.m. |
Created at: April 18, 2026, 6:07 a.m.