Triple
T29694134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M2-branes |
E751296
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | object in M-theory |
C48228
|
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: object in M-theory Context triple: [M2-branes, instanceOf, object in M-theory]
-
A.
type IIB supergravity background
A type IIB supergravity background is a ten-dimensional spacetime configuration of fields (metric, dilaton, axion, and form fields) that solves the classical equations of motion of type IIB supergravity, often serving as the low-energy limit of type IIB string theory.
-
B.
supergravity background
chosen
A supergravity background is a specific solution of supergravity field equations that defines a curved spacetime (often with fluxes and additional fields) in which strings or branes consistently propagate.
-
C.
supergravity solution
A supergravity solution is a specific configuration of fields (including the metric and superpartner fields) that satisfies the coupled equations of motion of a supergravity theory, often representing extended objects like branes or black holes in a higher-dimensional spacetime.
-
D.
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.
-
E.
object in general relativity
An object in general relativity is any localized concentration of energy–momentum whose presence curves spacetime and thereby influences the motion of matter and light.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:19 p.m.