Triple
T33588636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faddeev–Popov ghosts |
E860357
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Grassmann-valued field |
C17868
|
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: Grassmann-valued field Context triple: [Faddeev–Popov ghosts, instanceOf, Grassmann-valued field]
-
A.
class field theory
Class field theory is a branch of algebraic number theory that describes abelian extensions of number fields (or local fields) in terms of the arithmetic of the fields themselves, particularly their ideals and ideles.
-
B.
fermionic field
chosen
A fermionic field is a quantum field whose excitations correspond to particles with half-integer spin that obey Fermi–Dirac statistics and the Pauli exclusion principle.
-
C.
tensor field
A tensor field is a mathematical object that assigns a tensor (a multilinear map or multidimensional array following specific transformation rules) to every point in a space or manifold, varying smoothly from point to point.
-
D.
gauge theory
A gauge theory is a type of field theory in which the laws of physics are invariant under continuous local transformations of certain internal symmetries, leading to the introduction of gauge fields that mediate fundamental interactions.
-
E.
problem in field theory
A problem in field theory is a conceptual or computational question involving the properties, structures, and interactions of fields—such as scalar, vector, or gauge fields—typically formulated within the framework of classical or quantum field theory.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:40 a.m.