Triple
T36876952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bockstein homomorphism |
E911365
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | connecting homomorphism |
C65628
|
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: connecting homomorphism Context triple: [Bockstein homomorphism, instanceOf, connecting homomorphism]
-
A.
homomorphism
A homomorphism is a structure-preserving map between two algebraic objects (such as groups, rings, or vector spaces) that respects their defining operations.
-
B.
operation on homotopy groups
An operation on homotopy groups is a rule that takes one or more elements (or groups) of homotopy groups and produces new elements in (possibly other) homotopy groups in a way that respects their algebraic and topological structure.
-
C.
construction in homological algebra
chosen
A construction in homological algebra is a systematic process (such as forming chain complexes, derived functors, or spectral sequences) that builds new algebraic objects from given ones to study and encode their homological and cohomological properties.
-
D.
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.
-
E.
ring homomorphism
A ring homomorphism is a function between rings that preserves addition, multiplication, and the multiplicative identity (when present), mapping the structure of one ring compatibly into another.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.