Triple
T1095824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K⁺ |
E24268
|
entity |
| Predicate | hasDominantDecayBranchingRatio |
P3991
|
FINISHED |
| Object | ≈63.5% |
—
|
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: ≈63.5% | Statement: [K⁺, hasDominantDecayBranchingRatio, ≈63.5%]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDominantDecayBranchingRatio Context triple: [K⁺, hasDominantDecayBranchingRatio, ≈63.5%]
-
A.
hasBranchingRatioToHadrons
chosen
Indicates the fraction of a particle’s decays that result in hadronic final states (i.e., decays into hadrons).
-
B.
hasBranchingRatioToLeptons
Indicates the proportion of a particle’s decays that result in leptons among all its possible decay channels.
-
C.
decayWidth
Indicates the total probability per unit time (or corresponding energy measure) that an unstable particle will decay via all possible channels.
-
D.
dominantInBranch
Indicates that one entity holds primary control, influence, or authority over others within a specific branch or subdivision of a larger structure or organization.
-
E.
primaryDecayChannelStudied
Indicates that the primary mode of decay for a particle or system is the main subject of investigation or analysis.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b99ffb3481908cd168b6c58e1c6d |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b7448c148190a3c9a4158ebd05b4 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.