Triple
T10388611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Witten index |
E244832
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | supersymmetry index |
C24251
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: supersymmetry index Context triple: [Witten index, instanceOf, supersymmetry index]
-
A.
anomaly cancellation mechanism
An anomaly cancellation mechanism is a theoretical consistency requirement in quantum field theories whereby contributions from different fields or symmetries are arranged to exactly cancel gauge or gravitational anomalies, ensuring the preservation of gauge invariance and unitarity.
-
B.
superconductor type
A superconductor type is a classification of superconducting materials based on how they transition to and maintain superconductivity in the presence of external magnetic fields, typically distinguished as Type I or Type II.
-
C.
composite index
A composite index is a database index that combines multiple columns into a single index structure to optimize query performance on those combined fields.
-
D.
string theory concept
chosen
A string theory concept is an abstract element within the theoretical framework of string theory that represents fundamental entities, interactions, or symmetries as manifestations of one-dimensional vibrating strings in higher-dimensional spacetime.
-
E.
ultraviolet regularization method
An ultraviolet regularization method is a mathematical procedure used in quantum field theory to control and make sense of divergent high-energy (short-distance) contributions in integrals or sums by introducing a cutoff or modification at large momenta or energies.
- F. None of above.
Provenance (1 batch)
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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:05 p.m.