Triple
T34154900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beilinson regulator |
E876106
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cohomological construction |
C58003
|
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: cohomological construction Context triple: [Beilinson regulator, instanceOf, cohomological construction]
-
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.
cohomological invariant
chosen
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.
-
C.
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.
-
D.
topological construction
A topological construction is a method or process for building new topological spaces from given ones, typically by applying operations such as products, quotients, subspaces, or identifications.
-
E.
subset of cohomology
A subset of cohomology is a specified collection of cohomology classes within a given cohomology group, often chosen to capture particular geometric, topological, or algebraic properties.
- 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_69f349abaa508190a820f206620efddc |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:54 a.m.