Triple
T29694198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M5-branes |
E751297
|
entity |
| Predicate | R-symmetry |
P159578
|
FINISHED |
| Object | SO(5)_R |
—
|
NE NERFINISHED |
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: SO(5)_R | Statement: [M5-branes, R-symmetry, SO(5)_R]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: R-symmetry Context triple: [M5-branes, R-symmetry, SO(5)_R]
-
A.
hasSymmetryBreakingScale
Indicates that there is a characteristic energy or scale at which a symmetry of the system is broken.
-
B.
symmetryAlgebraOf
chosen
Indicates that one entity is the symmetry algebra associated with, or governing the symmetries of, the other entity.
-
C.
symmetryOf
Indicates that one entity is the symmetry counterpart or symmetric form of another entity, typically related by a specific symmetry operation or transformation.
-
D.
hasSupersymmetry
Indicates that a physical system, theory, or model exhibits supersymmetry, meaning there is a symmetry relating bosonic and fermionic degrees of freedom.
-
E.
isNonSupersymmetric
Indicates that the entity does not exhibit or obey supersymmetry, i.e., it lacks a symmetry relating bosons and fermions.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672af46e48190b76e9298e7d23eef |
completed | May 2, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:19 p.m.