Triple
T4700715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Neutron (1932 paper) |
E104261
|
entity |
| Predicate | usedRadiationSource |
P36680
|
FINISHED |
| Object | alpha particles from polonium |
—
|
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: alpha particles from polonium | Statement: [The Neutron (1932 paper), usedRadiationSource, alpha particles from polonium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedRadiationSource Context triple: [The Neutron (1932 paper), usedRadiationSource, alpha particles from polonium]
-
A.
usedRadioisotope
chosen
Indicates that one entity employed or applied a specific radioisotope in an action, process, or context involving another entity.
-
B.
usedAsSourceIn
Indicates that something serves as the origin, basis, or input from which another thing is derived, produced, or obtained.
-
C.
hasXRaySources
Indicates that an entity possesses or is associated with one or more X-ray emitting sources.
-
D.
appliedRadioisotopesIn
Indicates that radioisotopes were used or applied within a specified context, process, or location.
-
E.
usedResource
Indicates that an entity has utilized or consumed a particular resource in performing an action or achieving a result.
- 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd621ba7448190a53ab1e2897acf71 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:17 p.m.