Triple
T6788297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stokes' theorem |
E155868
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theorem in vector calculus |
C716
|
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: theorem in vector calculus Context triple: [Stokes' theorem, instanceOf, theorem in vector calculus]
-
A.
mathematical theorem
chosen
A mathematical theorem is a rigorously proven statement derived from axioms and previously established results, expressing a fundamental truth within a formal mathematical system.
-
B.
equation in the calculus of variations
An equation in the calculus of variations is a mathematical relation, typically an Euler–Lagrange equation, that characterizes the functions making a given functional stationary (usually minimizing or maximizing its value).
-
C.
vector space
A vector space is a set of objects called vectors, equipped with operations of vector addition and scalar multiplication that satisfy specific axioms such as associativity, commutativity, distributivity, and the existence of additive identities and inverses.
-
D.
result in mathematical physics
A result in mathematical physics is a rigorously proven statement that connects precise mathematical structures with physical theories, often clarifying, justifying, or predicting phenomena within a formal framework.
-
E.
Green’s function in Euclidean space
A Green’s function in Euclidean space is a fundamental solution to a linear differential operator that represents the response at one point due to a unit source located at another point, enabling the construction of solutions to boundary value problems via superposition.
- 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_69c6881770fc8190972b2906390380f5 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:14 p.m.