Triple
T38438290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euler–Poincaré characteristic formula |
E904009
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | topological invariant relation |
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: topological invariant relation Context triple: [Euler–Poincaré characteristic formula, instanceOf, topological invariant relation]
-
A.
differential-topological invariant
A differential-topological invariant is a quantity or property defined using smooth structures (like differentiable maps, vector fields, or differential forms) that remains unchanged under diffeomorphisms of manifolds.
-
B.
topological property
A topological property is a feature of a space that is preserved under homeomorphisms, meaning it remains unchanged under continuous deformations such as stretching or bending but not tearing or gluing.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.