Triple
T10803633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ornstein–Uhlenbeck process |
E254905
|
entity |
| Predicate | hasDriftTerm |
P38107
|
FINISHED |
| Object | θ(μ − X_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: θ(μ − X_t) | Statement: [Ornstein–Uhlenbeck process, hasDriftTerm, θ(μ − X_t)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDriftTerm Context triple: [Ornstein–Uhlenbeck process, hasDriftTerm, θ(μ − X_t)]
-
A.
hasDriftForm
chosen
Indicates that an entity possesses or is associated with a specific drift-related configuration, mode, or form.
-
B.
driftType
Indicates the manner or category of deviation or change from an expected or original state.
-
C.
hasDisplacement
Indicates a relationship where an entity experiences or is assigned a change in position or location from an initial point to a final point.
-
D.
hasKineticTerm
Indicates that an entity possesses a kinetic energy or motion-related term in its mathematical or physical description.
-
E.
hasDelta
Indicates that there is a change, difference, or deviation between two related states, values, or versions of something.
- 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_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. |
Created at: April 8, 2026, 9:18 p.m.