Triple
T23933517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klebanov–Tseytlin background |
E602565
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | string theory solution |
C19902
|
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: string theory solution Context triple: [Klebanov–Tseytlin background, instanceOf, string theory solution]
-
A.
string theory concept
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.
-
B.
magnetic monopole solution
A magnetic monopole solution is a theoretical field configuration in gauge or electromagnetic theory that describes an isolated, point-like source of magnetic charge consistent with the underlying equations of motion.
-
C.
solution in general relativity
A solution in general relativity is a specific spacetime metric (and accompanying matter fields, if any) that satisfies Einstein’s field equations for a given physical configuration or set of conditions.
-
D.
solution of classical field equations
chosen
A solution of classical field equations is a specific configuration of fields in space and time that satisfies the governing differential equations and boundary/initial conditions of a classical field theory.
-
E.
holographic duality
Holographic duality is a theoretical principle in physics stating that a gravitational theory in a higher-dimensional spacetime is exactly equivalent to a non-gravitational quantum field theory living on its lower-dimensional boundary.
- 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_69e2953cf6e081909b8e25a10a52dddc |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 17, 2026, 8:58 p.m.