Triple
T1261877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SU(2)_L |
E12518
|
entity |
| Predicate | relatedMixingAngle |
P26404
|
FINISHED |
| Object | Weinberg angle θ_W |
—
|
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: Weinberg angle θ_W | Statement: [SU(2)_L, relatedMixingAngle, Weinberg angle θ_W]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedMixingAngle Context triple: [SU(2)_L, relatedMixingAngle, Weinberg angle θ_W]
-
A.
decayWidth
Indicates the total probability per unit time (or corresponding energy measure) that an unstable particle will decay via all possible channels.
-
B.
hasBranchingRatioToLeptons
Indicates the proportion of a particle’s decays that result in leptons among all its possible decay channels.
-
C.
centerOfMassEnergy
Indicates the total energy available in the center-of-mass frame when two or more particles interact or collide.
-
D.
measuredNumberOfLightNeutrinoFamilies
Indicates the experimentally determined count of distinct light neutrino families inferred from measurements.
-
E.
hasAntiquark
Indicates that one particle is associated with, or contains, a corresponding antiquark as part of its composition or structure.
- F. None of above. chosen
Provenance (4 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bfc64e648190b9c4f980eb8168aa |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6eefbc81908dddd7d2ef368186 |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bd98b62c8190a5f6710345c0537d |
completed | March 1, 2026, 10:28 p.m. |
Created at: March 1, 2026, 7:50 p.m.