Triple
T5425790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Picard iteration |
E121358
|
entity |
| Predicate | typicalProblemForm |
P15680
|
FINISHED |
| Object | y'(t) = f(t,y(t)), y(t0) = y0 |
—
|
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: y'(t) = f(t,y(t)), y(t0) = y0 | Statement: [Picard iteration, typicalProblemForm, y'(t) = f(t,y(t)), y(t0) = y0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalProblemForm Context triple: [Picard iteration, typicalProblemForm, y'(t) = f(t,y(t)), y(t0) = y0]
-
A.
typicalForm
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
-
B.
problemStatement
chosen
Indicates that an entity presents, defines, or expresses a specific problem or issue to be addressed.
-
C.
problems
Indicates that one entity has issues, difficulties, or complications associated with or caused by another entity.
-
D.
questionForm
Indicates that one entity is expressed or structured in the form of a question directed toward another entity or context.
-
E.
helpedForm
Indicates that one entity contributed significantly to the creation, establishment, or founding of 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_69bd463b58d88190b258261573de9e91 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8911a7348190ad9378a248190f07 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd846b8bdc81909dcdc2a3084226f2 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:06 p.m.