Triple
T1096095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Z boson |
E24274
|
entity |
| Predicate | decaysVia |
P5370
|
FINISHED |
| Object | weak interaction |
—
|
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: weak interaction | Statement: [Z boson, decaysVia, weak interaction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decaysVia Context triple: [Z boson, decaysVia, weak interaction]
-
A.
decayWidth
Indicates the total probability per unit time (or corresponding energy measure) that an unstable particle will decay via all possible channels.
-
B.
decayMode
chosen
Indicates the specific process or pathway by which an unstable entity transforms or decays into other products.
-
C.
primaryDecayChannelStudied
Indicates that the primary mode of decay for a particle or system is the main subject of investigation or analysis.
-
D.
breaksDownWhen
Indicates that one entity becomes nonfunctional, damaged, or fails when subjected to the presence, action, or conditions imposed by another entity.
-
E.
hasBranchingRatioToHadrons
Indicates the fraction of a particle’s decays that result in hadronic final states (i.e., decays into hadrons).
- 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.