Triple
T12597466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | classical fourth-order Runge–Kutta method |
E300768
|
entity |
| Predicate | isSelfStarting |
P105626
|
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, isSelfStarting, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSelfStarting Context triple: [classical fourth-order Runge–Kutta method, isSelfStarting, true]
-
A.
isSelfSynchronizing
Indicates that a process, system, or component can automatically align its timing or state with others without requiring external coordination or control.
-
B.
isItsOwn
Indicates that an entity stands in the specified relation to itself, i.e., it is related to itself as its own counterpart or owner.
-
C.
isSelfSimilar
Indicates that an entity exhibits similarity to itself across different scales, parts, or transformations, often implying a recursive or fractal-like structure.
-
D.
considersItself
Indicates that an entity regards or perceives itself in a particular way, role, or state.
-
E.
selfInteracts
Indicates that an entity interacts with itself, rather than with a distinct external entity.
- 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.