Triple
T7150462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milstein method |
E166677
|
entity |
| Predicate | errorOrder |
P29588
|
FINISHED |
| Object | local truncation error of order Δt^{3/2} in strong sense |
—
|
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: local truncation error of order Δt^{3/2} in strong sense | Statement: [Milstein method, errorOrder, local truncation error of order Δt^{3/2} in strong sense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: errorOrder
Context triple: [Milstein method, errorOrder, local truncation error of order Δt^{3/2} in strong sense]
-
A.
errorTermOrder
chosen
Indicates the ordering or sequence in which error terms are arranged or considered relative to one another.
-
B.
orderOf
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
C.
subsequentOrder
Indicates that one order occurs after or follows another order in sequence.
-
D.
errorPhase
Indicates the specific stage or phase in a process or workflow during which an error occurred.
-
E.
orderedBy
Indicates that one entity has placed a request or purchase for another entity, typically specifying who initiated the order.
- 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_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. |
Created at: March 27, 2026, 2:46 p.m.