Triple
T26441289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HOMFLY-PT homology |
E665095
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | categorified knot invariant |
C27157
|
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: categorified knot invariant Context triple: [HOMFLY-PT homology, instanceOf, categorified knot invariant]
-
A.
3-manifold invariant
A 3-manifold invariant is a quantity or structure assigned to a 3-dimensional manifold that remains unchanged under homeomorphisms or diffeomorphisms, used to distinguish and classify such manifolds.
-
B.
quantum invariant
A quantum invariant is a quantity associated with a quantum system or topological object that remains unchanged under specified transformations, often used to distinguish or classify quantum states, knots, or manifolds.
-
C.
topological quantum field theory
A topological quantum field theory is a quantum field theory whose observables and correlation functions depend only on the topology of the underlying spacetime manifold, not on its geometric details such as distances or angles.
-
D.
concept in knot theory
A concept in knot theory is an abstract idea or construct used to study and classify embeddings of circles (knots) and collections of circles (links) in three-dimensional space up to continuous deformation.
-
E.
homological invariant
chosen
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_69ee883c851881909e2ab04efbb3c5fe |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 26, 2026, 11:58 p.m.