Triple
T36906020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dehn–Lickorish theorem |
E912779
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theorem in low-dimensional topology |
C44531
|
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: theorem in low-dimensional topology Context triple: [Dehn–Lickorish theorem, instanceOf, theorem in low-dimensional topology]
-
A.
technique in low-dimensional topology
A technique in low-dimensional topology is a method or procedure used to analyze, classify, or manipulate topological spaces and structures primarily in dimensions two, three, and four, often leveraging geometric, combinatorial, or algebraic tools.
-
B.
result in low-dimensional topology
chosen
A result in low-dimensional topology is a theorem or proposition that characterizes the structure, classification, or properties of topological spaces and manifolds of dimension four or less.
-
C.
work in geometric topology
Work in geometric topology studies the properties and structures of spaces that are preserved under continuous deformations, focusing on the interplay between geometry and topology in shapes and manifolds.
-
D.
invariant in geometric topology
An invariant in geometric topology is a property or quantity assigned to a topological or geometric object that remains unchanged under specified classes of deformations or equivalences, such as homeomorphisms or isotopies.
-
E.
3-manifold
A 3-manifold is a topological space in which every point has a neighborhood homeomorphic to three-dimensional Euclidean space \(\mathbb{R}^3\).
- 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.