Triple
T8832110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | antiprotonic helium |
E210169
|
entity |
| Predicate | decayMechanism |
P5370
|
FINISHED |
| Object | radiative de-excitation followed by annihilation |
—
|
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: radiative de-excitation followed by annihilation | Statement: [antiprotonic helium, decayMechanism, radiative de-excitation followed by annihilation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decayMechanism Context triple: [antiprotonic helium, decayMechanism, radiative de-excitation followed by annihilation]
-
A.
degradationMechanism
Indicates the process or mechanism by which something deteriorates, breaks down, or loses its original quality or function over time.
-
B.
decayMode
chosen
Indicates the specific process or pathway by which an unstable entity transforms or decays into other products.
-
C.
decayResistanceCause
Indicates that one factor or condition is the cause of another entity’s resistance to decay.
-
D.
killMechanism
Indicates the method or process by which one entity causes the death or destruction of another.
-
E.
formationMechanism
Indicates the process or mechanism by which something is formed, created, or brought into existence.
- 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_69ca8365b28081909e48e45e95dfc405 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc605005788190a4df1fe317f3056a |
completed | April 1, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69cc5c23d08481908d8c9b0ad3d1dc00 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:47 p.m.