Triple
T29992732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | positronium |
E761922
|
entity |
| Predicate | paraPositroniumDecayProducts |
P118978
|
FINISHED |
| Object | two gamma photons |
—
|
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: two gamma photons | Statement: [positronium, paraPositroniumDecayProducts, two gamma photons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paraPositroniumDecayProducts Context triple: [positronium, paraPositroniumDecayProducts, two gamma photons]
-
A.
decayProduct
chosen
Indicates that one entity is the resulting product formed when another entity undergoes a decay process.
-
B.
betaPlusBranchingRatio
Indicates the fraction of all decays of an unstable nucleus that proceed specifically via beta-plus (positron) emission.
-
C.
betaDecayInvolves
Indicates that a beta decay process includes or is characterized by the participation of a specified particle, product, or sub-process.
-
D.
antiparticleType
Indicates that one particle is the corresponding antiparticle type of another particle.
-
E.
antiprotonsProducedIn
Indicates that antiprotons are generated, created, or produced within or by a specified process, system, or location.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6791c8e088190a0766badc1d3b5cd |
completed | May 2, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 6:39 p.m.