Triple
T2731235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Itô process |
E60316
|
entity |
| Predicate | generalForm |
P12789
|
FINISHED |
| Object | X_t = X_0 + ∫_0^t a_s ds + ∫_0^t b_s dW_s |
—
|
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 = X_0 + ∫_0^t a_s ds + ∫_0^t b_s dW_s | Statement: [Itô process, generalForm, X_t = X_0 + ∫_0^t a_s ds + ∫_0^t b_s dW_s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: generalForm Context triple: [Itô process, generalForm, X_t = X_0 + ∫_0^t a_s ds + ∫_0^t b_s dW_s]
-
A.
generalizedForm
Indicates that one entity is a more abstract, generalized version or broader form of another entity.
-
B.
standardFormulation
Indicates that something is expressed or represented in a conventional, officially accepted, or commonly used form or version.
-
C.
standardFormUsedIn
Indicates that a particular standard form is employed or applied within a given context, process, or system.
-
D.
logicalForm
Indicates a relationship where an expression is associated with its structured, formal logical representation.
-
E.
typicalForm
chosen
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
- 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_69ab4b75cd908190b691ef0d1801acda |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdaee29088190bc4c734e48995794 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd82586f88190a98f60d3247fe2d3 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.