Triple
T24806485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verdier duality |
E620670
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theorem in homological algebra |
C716
|
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: theorem in homological algebra Context triple: [Verdier duality, instanceOf, theorem in homological algebra]
-
A.
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.
-
B.
cohomology theory
A cohomology theory is a functorial assignment of graded algebraic invariants to topological spaces (or other mathematical objects) that encodes global structural and obstruction information via axioms such as exactness and homotopy invariance.
-
C.
mathematical theorem
chosen
A mathematical theorem is a rigorously proven statement derived from axioms and previously established results, expressing a fundamental truth within a formal mathematical system.
-
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.
tool in algebraic topology
A tool in algebraic topology is a conceptual or computational method—such as homology, cohomology, or spectral sequences—used to translate topological problems into algebraic ones to analyze and classify topological spaces.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 4:50 a.m.