Triple
T16249625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laplacian spectrum |
E394466
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | spectral invariant |
C10588
|
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: spectral invariant Context triple: [Laplacian spectrum, instanceOf, spectral invariant]
-
A.
geometric invariant
chosen
A geometric invariant is a property of a geometric object that remains unchanged under a specified group of transformations, such as rotations, translations, or more general symmetries.
-
B.
homological invariant
A homological invariant is a quantity or structure derived from homology theory that remains unchanged under specified transformations, used to distinguish and classify mathematical objects up to an appropriate notion of equivalence.
-
C.
spectroscopic approximation
A spectroscopic approximation is a simplified theoretical or computational model used to estimate spectroscopic properties (such as energy levels, transition frequencies, or intensities) by neglecting or approximating certain physical effects to make calculations tractable.
-
D.
spectral sequence
A spectral sequence is an algebraic tool in homological algebra and algebraic topology that computes complex (co)homology groups via a sequence of successive approximations organized in pages linked by differentials.
-
E.
classical invariant
A classical invariant is a quantity or property associated with a mathematical object that remains unchanged under a specified group of classical transformations, such as rotations, translations, or linear changes of coordinates.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:04 a.m.