Triple
T33588686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilson loop |
E860358
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | concept in gauge theory |
C1454
|
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: concept in gauge theory Context triple: [Wilson loop, instanceOf, concept in gauge theory]
-
A.
gauge theory
chosen
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.
-
B.
gauge field
A gauge field is a field that mediates interactions between particles by enforcing local gauge symmetries, typically represented mathematically by connection fields associated with a symmetry group.
-
C.
concept in vector calculus
A concept in vector calculus is an abstract idea or principle involving vector-valued functions and operations—such as gradients, divergences, curls, and line or surface integrals—that describes how quantities with both magnitude and direction vary in space.
-
D.
concept in classical electromagnetism
A concept in classical electromagnetism represents a fundamental idea or quantity—such as electric field, magnetic flux, or charge—that describes how electric and magnetic phenomena are generated, interact, and propagate in space and time.
-
E.
concept in Lie theory
A concept in Lie theory is an abstract mathematical construct—such as a Lie group, Lie algebra, or representation—that captures continuous symmetries and their algebraic and geometric properties.
- 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.