Triple
T33535614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | proof of the Milnor conjecture |
E858913
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | result in Galois cohomology |
C24993
|
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 Galois cohomology Context triple: [proof of the Milnor conjecture, instanceOf, result in Galois cohomology]
-
A.
result in arithmetic geometry
chosen
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 group theory
A result in group theory is a proven statement or theorem about the algebraic structure and properties of groups and their related constructs.
-
C.
result in equivariant cohomology
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.
-
D.
cohomological invariant
A cohomological invariant is a rule that assigns to each object in a given class (such as algebraic varieties, groups, or topological spaces) an element of a cohomology group in a way that is functorial and captures structural or classification information about those objects.
-
E.
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.
- 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_69f34978caf4819083f90eba4944d8e8 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:39 a.m.