Triple
T6833275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richardson iteration |
E157388
|
entity |
| Predicate | updateFormula |
P24049
|
FINISHED |
| Object | x_{k+1} = x_k + \,\omega\,(b - A x_k) |
—
|
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: x_{k+1} = x_k + \,\omega\,(b - A x_k) | Statement: [Richardson iteration, updateFormula, x_{k+1} = x_k + \,\omega\,(b - A x_k)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updateFormula
Context triple: [Richardson iteration, updateFormula, x_{k+1} = x_k + \,\omega\,(b - A x_k)]
-
A.
updatesSpecificationOf
Indicates that one entity revises, modifies, or replaces the existing specification of another entity.
-
B.
updated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
C.
formulaUsed
chosen
Indicates that a particular formula is employed or applied in performing a calculation, derivation, or reasoning step.
-
D.
updateProcess
Indicates the action or procedure by which an existing item, system, or state is modified to a newer or revised version.
-
E.
updatesVersionOf
Indicates that one entity is a newer or modified version that replaces or supersedes another entity.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d62b1e8c8190a81d91191a54b073 |
completed | March 27, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69c6d09d95f0819091ca7f897dc21efe |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.