Triple
T10803615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ornstein–Uhlenbeck process |
E254905
|
entity |
| Predicate | hasSDEForm |
P95548
|
FINISHED |
| Object | dX_t = θ(μ − X_t) dt + σ dW_t |
—
|
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: dX_t = θ(μ − X_t) dt + σ dW_t | Statement: [Ornstein–Uhlenbeck process, hasSDEForm, dX_t = θ(μ − X_t) dt + σ dW_t]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSDEForm Context triple: [Ornstein–Uhlenbeck process, hasSDEForm, dX_t = θ(μ − X_t) dt + σ dW_t]
-
A.
isFormedFor
Indicates that something is created, established, or brought into existence for a particular purpose, function, or beneficiary.
-
B.
hasDuneType
Indicates that one entity is characterized by or associated with a specific type or classification of dune.
-
C.
hasScalarForm
Indicates that something possesses or can be represented in a single-valued (scalar) form rather than as a vector, matrix, or more complex structure.
-
D.
hasFieldFormation
Indicates that an entity possesses or exhibits a particular field formation, such as a structured arrangement or configuration of fields.
-
E.
hasSymbolicForm
Indicates that one entity serves as the symbolic representation or abstract form of another entity.
- 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7336feff88190b638b7d62d34da0e |
completed | April 9, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69d6f3188f00819094ee8d65b187a333 |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa334b8c819082eaf8537084c323 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:18 p.m.