Triple
T25979609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | four-momentum operator |
E646031
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | relativistic operator |
C36563
|
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: relativistic operator Context triple: [four-momentum operator, instanceOf, relativistic operator]
-
A.
relativistic Hamiltonian
A relativistic Hamiltonian is an energy operator or function in classical or quantum mechanics that generates time evolution while consistently incorporating the principles of special relativity, typically ensuring Lorentz invariance and relativistic energy-momentum relations.
-
B.
relativistic wave equation
A relativistic wave equation is a differential equation, such as the Klein–Gordon or Dirac equation, that describes how quantum fields or particles evolve in space and time in a way consistent with the principles of special relativity.
-
C.
Hilbert space operator
chosen
A Hilbert space operator is a linear transformation defined on a (subspace of a) Hilbert space that maps vectors to vectors in a way compatible with the space’s inner product structure, often studied via its continuity, boundedness, and spectral properties.
-
D.
geometric operator
A geometric operator is a mathematical construct that acts on geometric objects (such as points, vectors, or shapes) to transform, relate, or measure them while respecting the underlying geometric structure.
-
E.
linear differential operator
A linear differential operator is a mapping that takes a function as input and returns a new function formed by a linear combination of the function and its derivatives.
- 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 8:54 a.m.