Triple
T24806419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lorenz attractor |
E620668
|
entity |
| Predicate | equationSystem |
P157326
|
FINISHED |
| Object | dy/dt = x (ρ − z) − y |
—
|
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: dy/dt = x (ρ − z) − y | Statement: [Lorenz attractor, equationSystem, dy/dt = x (ρ − z) − y]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equationSystem Context triple: [Lorenz attractor, equationSystem, dy/dt = x (ρ − z) − y]
-
A.
equationSystem
chosen
Indicates that multiple equations are collectively related as a system that must be satisfied simultaneously.
-
B.
coefficientSystems
Indicates a relationship where specific numerical or algebraic coefficients are assigned or associated with a system, structure, or set of elements.
-
C.
numberOfEquations
Indicates the total count of equations associated with or involved in a given entity or context.
-
D.
requiresSolvingAlgebraicEquations
Indicates that performing or completing an action depends on solving algebraic equations.
-
E.
supportsEquations
Indicates that one entity provides the capability to handle, display, or work with mathematical equations for another entity or within a given context.
- F. None of above.
Provenance (3 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 4:50 a.m.