Triple
T32368584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zassenhaus conjecture |
E827066
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | open problem in group theory |
C60627
|
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: open problem in group theory Context triple: [Zassenhaus conjecture, instanceOf, open problem in group theory]
-
A.
open problem in graph theory
An open problem in graph theory is a well-defined question about graphs whose truth or solution is currently unknown and remains an active subject of mathematical research.
-
B.
open problem in combinatorics
An open problem in combinatorics is an unsolved question about discrete structures or counting principles whose resolution remains unknown despite significant mathematical investigation.
-
C.
open problem in number theory
An open problem in number theory is an unsolved question about the properties or relationships of integers, primes, or related numerical structures that remains unproven despite significant mathematical investigation.
-
D.
collection of decision problems in group theory
A collection of decision problems in group theory is a conceptual class comprising questions that ask, for various groups and inputs, whether certain algebraic properties or relations hold, such as the word, conjugacy, or isomorphism problems.
-
E.
open problem in operator algebras
An open problem in operator algebras is an unresolved, precisely formulated question about the structure, classification, or properties of operator algebras and their morphisms, whose solution is currently unknown despite active research.
- F. None of above. chosen
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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:50 a.m.