Triple
T5499112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W− boson |
E144282
|
entity |
| Predicate | hasDecayWidth |
P5365
|
FINISHED |
| Object | about 2.085 GeV |
—
|
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: about 2.085 GeV | Statement: [W− boson, hasDecayWidth, about 2.085 GeV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDecayWidth Context triple: [W− boson, hasDecayWidth, about 2.085 GeV]
-
A.
decayWidth
chosen
Indicates the total probability per unit time (or corresponding energy measure) that an unstable particle will decay via all possible channels.
-
B.
hasBranchingRatioToHadrons
Indicates the fraction of a particle’s decays that result in hadronic final states (i.e., decays into hadrons).
-
C.
hasMeanLifetime
Indicates the characteristic average time duration for which an entity, state, or condition persists before it decays, ends, or changes.
-
D.
decayMode
Indicates the specific process or pathway by which an unstable entity transforms or decays into other products.
-
E.
hasBranchingRatioToLeptons
Indicates the proportion of a particle’s decays that result in leptons among all its possible decay channels.
- 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_69c008f5a2748190bce7a39aabf87a6d |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f08c2a4819093e772a1497c7ecc |
completed | March 22, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69c01b052f3c81909f71c6add0f35a6f |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:32 p.m.