Triple
T6833288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richardson iteration |
E157388
|
entity |
| Predicate | canBePreconditionedBy |
P14814
|
FINISHED |
| Object | left preconditioner |
—
|
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: left preconditioner | Statement: [Richardson iteration, canBePreconditionedBy, left preconditioner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBePreconditionedBy Context triple: [Richardson iteration, canBePreconditionedBy, left preconditioner]
-
A.
hasPrecedingCondition
Indicates that one condition occurs or exists before another condition in time or sequence.
-
B.
precondition
chosen
Indicates that one event, state, or condition must be true or occur before another event, state, or condition can validly or successfully take place.
-
C.
canBePerformed
Indicates that a particular action or activity is possible to carry out under given conditions or by a specified agent.
-
D.
canBeInvokedBy
Indicates that one entity (such as a function, method, or operation) is able to be called, triggered, or executed by another entity.
-
E.
mayBeFollowedBy
Indicates that one event, state, or item is allowed or able to occur immediately after another in a sequence.
- 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.