Triple
T22854682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Centrifuge Plant (planned) |
E566446
|
entity |
| Predicate | intendedIsotope |
P149990
|
FINISHED |
| Object | uranium-235 |
—
|
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: uranium-235 | Statement: [American Centrifuge Plant (planned), intendedIsotope, uranium-235]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedIsotope Context triple: [American Centrifuge Plant (planned), intendedIsotope, uranium-235]
-
A.
commonIsotope
Indicates that two substances share the same most naturally abundant isotope of an element.
-
B.
naturalIsotope
Indicates that one entity is a naturally occurring isotope form of another element or nuclide.
-
C.
isLighterIsotopeOf
Indicates that one isotope has a lower atomic mass (fewer neutrons) than another isotope of the same element.
-
D.
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.
-
E.
isNucleusOfIsotope
Indicates that a given nucleus belongs to and characterizes a specific isotope.
- 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17ebb4ea48190b4b865e316f6a75f |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
| PDg | Predicate description generation | batch_69eeeb577e2081909f4a4e9c296535c0 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:37 p.m.