Triple
T34471747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nisnevich topology |
E884926
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Grothendieck topology |
C27156
|
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: Grothendieck topology Context triple: [Nisnevich topology, instanceOf, Grothendieck topology]
-
A.
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.
-
B.
topology
Topology is the mathematical study of properties of spaces that are preserved under continuous deformations such as stretching or bending, but not tearing or gluing.
-
C.
topological algebra
A topological algebra is an algebra over a field that is also a topological vector space, where the algebraic operations (addition, scalar multiplication, and multiplication) are continuous with respect to the topology.
-
D.
area of algebraic geometry
chosen
An area of algebraic geometry is a subfield focused on a specific collection of problems, techniques, and structures related to the study of solutions to polynomial equations and their geometric properties.
-
E.
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.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:01 a.m.