Triple
T17040882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | theta-method |
E413442
|
entity |
| Predicate | orderOfAccuracy |
P105618
|
FINISHED |
| Object | first order for theta ≠ 1/2 |
—
|
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: first order for theta ≠ 1/2 | Statement: [theta-method, orderOfAccuracy, first order for theta ≠ 1/2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderOfAccuracy Context triple: [theta-method, orderOfAccuracy, first order for theta ≠ 1/2]
-
A.
hasLocalTruncationErrorOrder
chosen
Indicates the order or degree to which a local truncation error term appears or dominates in a numerical or analytical approximation.
-
B.
accuracyOrderSpace
Indicates the ordering of entities based on their relative level of accuracy within a defined space or context.
-
C.
orderOfNewtonCotes
Indicates the numerical integration rule’s order in the Newton–Cotes family used to approximate an integral.
-
D.
errorTermOrder
Indicates the ordering or sequence in which error terms are arranged or considered relative to one another.
-
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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d8f6a0c08190a838279b83b55b72 |
completed | April 18, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.