Triple
T28421066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Demon core |
E719940
|
entity |
| Predicate | plutoniumIsotope |
P118704
|
FINISHED |
| Object | plutonium-239 |
—
|
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: plutonium-239 | Statement: [Demon core, plutoniumIsotope, plutonium-239]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plutoniumIsotope Context triple: [Demon core, plutoniumIsotope, plutonium-239]
-
A.
producedPlutoniumFor
Indicates that one entity generated or manufactured plutonium intended for use by another entity.
-
B.
plutoniumFacility
Indicates a facility that is involved in the production, processing, handling, or storage of plutonium.
-
C.
isTransuranic
Indicates that an element has an atomic number greater than that of uranium, placing it beyond uranium in the periodic table.
-
D.
radioactiveIsotope
chosen
Indicates that one entity is a radioactive isotope of another, meaning it is an unstable nuclide of the same element that undergoes radioactive decay.
-
E.
typeOfIsotopesProduced
Indicates the kinds or categories of isotopes that are generated or produced by a given process, source, or entity.
- 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_69eff6f1c5088190bc24bfbf92f9c017 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:33 a.m.