Triple
T12597452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | classical fourth-order Runge–Kutta method |
E300768
|
entity |
| Predicate | usesStepSizeSymbol |
P96497
|
FINISHED |
| Object | h |
—
|
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: h | Statement: [classical fourth-order Runge–Kutta method, usesStepSizeSymbol, h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStepSizeSymbol Context triple: [classical fourth-order Runge–Kutta method, usesStepSizeSymbol, h]
-
A.
stepSizeSymbol
chosen
Indicates the symbolic representation used to denote the size or magnitude of a step in a process, sequence, or operation.
-
B.
smallerStepSizeEffect
Indicates that using a smaller step size in a process or algorithm produces a particular effect or change in its behavior or outcome.
-
C.
numberOfStepsSymbolism
Indicates the symbolic or thematic meaning associated with a specific number of steps in a sequence, process, or structure.
-
D.
stepTakes
Indicates that one step directly follows or is taken after another step in a process or sequence.
-
E.
isStepToward
Indicates that one action, state, or condition serves as progress or a necessary move in the direction of achieving another.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:08 p.m.