Triple
T2815520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euler’s method for numerical integration |
E54272
|
entity |
| Predicate | globalErrorOrder |
P29588
|
FINISHED |
| Object | O(h) |
—
|
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: O(h) | Statement: [Euler’s method for numerical integration, globalErrorOrder, O(h)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: globalErrorOrder Context triple: [Euler’s method for numerical integration, globalErrorOrder, O(h)]
-
A.
errorTermOrder
chosen
Indicates the ordering or sequence in which error terms are arranged or considered relative to one another.
-
B.
errorRecovery
Indicates that an entity detects a failure or error condition and initiates actions to restore normal or acceptable operation.
-
C.
errorPropagation
Indicates how an error in one component, process, or variable is transmitted to and affects other components, processes, or variables in a system.
-
D.
errorHandlingModel
Indicates how a system or component manages, responds to, and recovers from errors or exceptional conditions during operation.
-
E.
orderOf
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
- 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_69ab49de0af08190b3da69683be1e728 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde4d29488190a32461906dd9ea7e |
completed | March 7, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69abdd0740208190911dc9c9546a79ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.