Triple
T12597474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | classical fourth-order Runge–Kutta method |
E300768
|
entity |
| Predicate | isNotAStiffSolver |
P105628
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [classical fourth-order Runge–Kutta method, isNotAStiffSolver, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNotAStiffSolver Context triple: [classical fourth-order Runge–Kutta method, isNotAStiffSolver, true]
-
A.
isExactlySolvable
Indicates that a problem, model, or equation can be solved completely and exactly (without approximation) using known analytical or algorithmic methods.
-
B.
admitsSolution
Indicates that a problem, system, or situation allows for or possesses at least one valid solution.
-
C.
hasEquationOfMotion
Indicates that one entity specifies or is associated with the equation of motion governing the dynamical behavior of another entity.
-
D.
isOneStepMethod
Indicates that a method or process completes the intended task in a single, indivisible step or operation.
-
E.
isSolutionOf
Indicates that one entity is a correct answer or satisfies the conditions of a given problem, equation, or task.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9559458dc8190bc4d6e697e99d70e |
completed | April 10, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69d9541894fc8190a0c3706a414279f0 |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d95590a5e08190842b988531cf2921 |
completed | April 10, 2026, 7:54 p.m. |
Created at: April 9, 2026, 5:08 p.m.