Triple
T22328782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hard Lefschetz theorem |
E551969
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | result in Hodge theory |
C28593
|
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: result in Hodge theory Context triple: [Hard Lefschetz theorem, instanceOf, result in Hodge theory]
-
A.
result in arithmetic geometry
A result in arithmetic geometry is a theorem or proposition that connects number-theoretic properties of solutions to polynomial equations with the geometric structure of the varieties they define over arithmetic fields.
-
B.
result in K-theory
A result in K-theory is a theorem or proposition describing how algebraic K-groups behave or relate to other invariants, often revealing deep structural or categorical properties of rings, schemes, or topological spaces.
-
C.
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.
-
D.
result in equivariant cohomology
chosen
A result in equivariant cohomology is a theorem or statement describing how cohomological invariants behave under a group action, typically relating equivariant cohomology groups to ordinary cohomology or geometric data of the action.
-
E.
result in lattice theory
A result in lattice theory is a proven theorem or proposition that describes structural, order-theoretic, or algebraic properties of lattices and their related constructs.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:43 p.m.