Triple
T34546141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brown representability theorem |
E886929
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | result in homotopy theory |
C49603
|
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 homotopy theory Context triple: [Brown representability theorem, instanceOf, result in homotopy theory]
-
A.
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.
-
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.
result in category theory
chosen
A result in category theory is a proven statement—such as a theorem, lemma, or proposition—about objects, morphisms, and functors that reveals structural relationships or properties within or between categories.
-
D.
tool in algebraic topology
A tool in algebraic topology is a conceptual or computational method—such as homology, cohomology, or spectral sequences—used to translate topological problems into algebraic ones to analyze and classify topological spaces.
-
E.
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.
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:02 a.m.