Triple
T19377321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coulomb gap |
E484704
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | many-body effect |
C19055
|
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: many-body effect Context triple: [Coulomb gap, instanceOf, many-body effect]
-
A.
many-body quantum system
A many-body quantum system is a collection of a large number of interacting quantum particles whose collective behavior exhibits complex phenomena that cannot be understood by considering the particles individually.
-
B.
quantum many-body theory
Quantum many-body theory studies systems of a large number of interacting quantum particles, aiming to understand their collective behavior and emergent phenomena using quantum mechanics and statistical methods.
-
C.
nonperturbative effect
chosen
A nonperturbative effect is a physical phenomenon that cannot be captured by any finite-order expansion in a small parameter (such as a coupling constant) and instead arises from intrinsically non-linear or exponentially suppressed contributions, like instantons or tunneling.
-
D.
technique in quantum many-body physics
A technique in quantum many-body physics is a systematic method or computational framework used to analyze, approximate, or simulate the collective behavior and emergent properties of interacting quantum particles.
-
E.
topological phase effect
A topological phase effect is a physical phenomenon where a system acquires a phase shift determined solely by the global, topological properties of its configuration space or path, rather than by local dynamical details.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:35 p.m.