Triple
T6801160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poincaré recurrence theorem |
E156189
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | result in dynamical systems |
C15689
|
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: result in dynamical systems Context triple: [Poincaré recurrence theorem, instanceOf, result in dynamical systems]
-
A.
result in mathematical physics
chosen
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.
-
B.
result in real analysis
In real analysis, a result is a proven mathematical statement—such as a theorem, lemma, proposition, or corollary—that establishes a specific property or relationship about real-valued functions, sequences, sets, or structures on the real numbers.
-
C.
result in complex analysis
A result in complex analysis is a proven statement or theorem about functions of a complex variable, often revealing deep relationships between analytic, geometric, and topological properties in the complex plane.
-
D.
stability concept in functional equations
A stability concept in functional equations studies how small deviations from an exact functional relationship affect the existence and form of nearby exact solutions, typically quantifying when approximate solutions imply true solutions close in some specified sense.
-
E.
ode
An ode is a lyrical poem, often formal and elevated in style, that expresses praise, admiration, or deep reflection on a particular subject.
- 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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:16 p.m.