Triple
T7150443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milstein method |
E166677
|
entity |
| Predicate | usesIncrement |
P75142
|
FINISHED |
| Object | Brownian motion increment |
—
|
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: Brownian motion increment | Statement: [Milstein method, usesIncrement, Brownian motion increment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesIncrement Context triple: [Milstein method, usesIncrement, Brownian motion increment]
-
A.
increasesWith
Indicates that as the value or magnitude of one entity grows, the value or magnitude of another entity correspondingly grows as well.
-
B.
subsequentIncrease
Indicates that one quantity or value increases after a prior event, state, or change has occurred.
-
C.
firstIncreaseIn
Indicates the point or event at which a quantity or value begins to increase for the first time in a given sequence or process.
-
D.
increases
Indicates that one entity causes another entity’s value, level, or intensity to become larger or higher.
-
E.
typicalTargetIncrement
Indicates the usual or expected amount by which a target value is intended to increase in a given adjustment or period.
- 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7f28b188190b1732ca711666531 |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1caf4e48190b47bb398a3c1554d |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a213508190a40aca39f9eee7d5 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:46 p.m.