Triple
T1261876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SU(2)_L |
E12518
|
entity |
| Predicate | breaksAtEnergyScale |
P23068
|
FINISHED |
| Object | electroweak scale (~246 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: electroweak scale (~246 GeV) | Statement: [SU(2)_L, breaksAtEnergyScale, electroweak scale (~246 GeV)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breaksAtEnergyScale Context triple: [SU(2)_L, breaksAtEnergyScale, electroweak scale (~246 GeV)]
-
A.
breaksDownWhen
Indicates that one entity becomes nonfunctional, damaged, or fails when subjected to the presence, action, or conditions imposed by another entity.
-
B.
beamEnergy
Indicates the amount of energy carried by or assigned to a beam in a physical or engineered system.
-
C.
typicalEnergyRange
Indicates the usual or characteristic range of energy values associated with an entity, process, or interaction.
-
D.
energyRegime
chosen
Indicates the specific range or mode of energy conditions under which a process, interaction, or system operates or is characterized.
-
E.
beamEnergyAfterUpgrade
Indicates the energy level of a beam following an upgrade or enhancement to the system that produces or accelerates it.
- 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_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. |
Created at: March 1, 2026, 7:50 p.m.