Triple
T15155065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poynting theorem |
E362048
|
entity |
| Predicate | hasDifferentialForm |
P117539
|
FINISHED |
| Object | ∂u/∂t + ∇·S + J·E = 0 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: ∂u/∂t + ∇·S + J·E = 0 | Statement: [Poynting theorem, hasDifferentialForm, ∂u/∂t + ∇·S + J·E = 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDifferentialForm Context triple: [Poynting theorem, hasDifferentialForm, ∂u/∂t + ∇·S + J·E = 0]
-
A.
hasDifferentials
Indicates that one entity possesses or is associated with differential components, mechanisms, or calculations relative to another entity.
-
B.
isDifferential
Indicates that one quantity represents the infinitesimal change or derivative of another with respect to a given variable.
-
C.
hasDerivative
Indicates that one entity is derived, obtained, or produced from another through some transformation, process, or modification.
-
D.
hasDerivatives
Indicates that one entity is derived, obtained, or developed from another entity.
-
E.
differential
Indicates a relationship where one quantity or state is defined as the infinitesimal change or difference relative to another variable or function.
- F. None of above. chosen
Provenance (4 batches)
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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0060b0cd08190afad14cffcc7d93f |
completed | April 15, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:08 a.m.