Triple
T24810848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green's theorem |
E620783
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | two-dimensional case of Stokes' theorem |
C29203
|
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: two-dimensional case of Stokes' theorem Context triple: [Green's theorem, instanceOf, two-dimensional case of Stokes' theorem]
-
A.
concept in vector calculus
chosen
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.
-
B.
simply connected surface
A simply connected surface is a two-dimensional topological space in which every closed loop can be continuously contracted to a point without leaving the surface.
-
C.
(0,2)-tensor
A (0,2)-tensor is a bilinear map that takes two vectors as input and returns a scalar, often representing objects like metrics or covariant tensor fields on a vector space or manifold.
-
D.
two-dimensional representation
A two-dimensional representation is a mapping of abstract elements or data into a flat plane using two axes or coordinates, enabling visualization and analysis of relationships in two spatial dimensions.
-
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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 4:50 a.m.