Triple
T16492982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wu experiment |
E400610
|
entity |
| Predicate | usedIsotope |
P36680
|
FINISHED |
| Object | cobalt-60 |
—
|
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: cobalt-60 | Statement: [Wu experiment, usedIsotope, cobalt-60]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedIsotope Context triple: [Wu experiment, usedIsotope, cobalt-60]
-
A.
usedRadioisotope
chosen
Indicates that one entity employed or applied a specific radioisotope in an action, process, or context involving another entity.
-
B.
commonIsotope
Indicates that two substances share the same most naturally abundant isotope of an element.
-
C.
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.
-
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.
naturalIsotope
Indicates that one entity is a naturally occurring isotope form of another element or nuclide.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e30cb648190a52cb32896c4ac5a |
completed | April 18, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:13 a.m.