Triple

T32258809
Position Surface form Disambiguated ID Type / Status
Subject Koksma–Hlawka inequality E824092 entity
Predicate errorBoundDependsOn P43797 FINISHED
Object variation of the integrand 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: variation of the integrand | Statement: [Koksma–Hlawka inequality, errorBoundDependsOn, variation of the integrand]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: errorBoundDependsOn
Context triple: [Koksma–Hlawka inequality, errorBoundDependsOn, variation of the integrand]
  • A. orderDependentBound
    Indicates that one entity’s value or behavior is constrained by another in a way that depends on the specific ordering or sequence in which they are considered or applied.
  • B. accuracyDependsOn chosen
    Indicates that the accuracy of one entity or process is contingent upon, or influenced by, another entity or factor.
  • C. givesBoundOn
    Indicates that one quantity provides an upper or lower limit (a bound) on the value or behavior of another quantity.
  • D. errorProbabilityBound
    Indicates that there is an upper limit or constraint on the probability that an error will occur in a given process or system.
  • E. errorSide
    Indicates the side, party, or component on which an error occurs or is attributed in a given context.
  • 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_69f3490db0748190bfef6e50c95d39d3 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6bc5652e08190b519631b7d497e75 completed May 3, 2026, 3:09 a.m.
PD Predicate disambiguation batch_69f6ba6cef208190bc5cd43d96127004 completed May 3, 2026, 3:01 a.m.
Created at: May 1, 2026, 12:41 a.m.