Triple
T18792980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilbert class field |
E459562
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | object in algebraic number theory |
C21313
|
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: object in algebraic number theory Context triple: [Hilbert class field, instanceOf, object in algebraic number theory]
-
A.
algebraic number field
chosen
An algebraic number field is a finite field extension of the rational numbers, obtained by adjoining to ℚ a root of a nonzero polynomial with rational (or integer) coefficients.
-
B.
algebraic number
An algebraic number is any complex number that is a root of a nonzero polynomial equation with integer (or equivalently, rational) coefficients.
-
C.
object in invariant theory
An object in invariant theory is a mathematical entity, such as a vector space, polynomial ring, or group action, whose structure and symmetries are studied through the functions or quantities that remain unchanged under a specified group of transformations.
-
D.
object of analytic number theory
An object of analytic number theory is a mathematical entity—such as a function, sequence, or set of numbers—studied using tools of analysis (like complex analysis, Fourier analysis, or measure theory) to understand the distribution and properties of integers and related structures.
-
E.
result in arithmetic geometry
A result in arithmetic geometry is a theorem or proposition that connects number-theoretic properties of solutions to polynomial equations with the geometric structure of the varieties they define over arithmetic fields.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:53 a.m.