Triple

T7871609
Position Surface form Disambiguated ID Type / Status
Subject Jacobi elliptic functions E182748 entity
Predicate haveLimit P9149 FINISHED
Object trigonometric functions as m → 0 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: trigonometric functions as m → 0 | Statement: [Jacobi elliptic functions, haveLimit, trigonometric functions as m → 0]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: haveLimit
Context triple: [Jacobi elliptic functions, haveLimit, trigonometric functions as m → 0]
  • A. isLimitOf chosen
    Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
  • B. hasLimitation
    Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
  • C. gLimit
    Indicates a constraint or maximum boundary imposed on the magnitude, rate, or extent of something within a given context.
  • D. canBeExceededIn
    Indicates that one entity’s value, level, or extent is capable of being surpassed by that of another entity within a specified context.
  • E. supportsRateLimiting
    Indicates that one entity provides or is compatible with mechanisms to restrict the rate at which another entity can perform actions or process requests.
  • 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_69ca82894d9081908a832bfce71a4714 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb39a5950481908399211c5dfe2569 completed March 31, 2026, 3:04 a.m.
PD Predicate disambiguation batch_69cae928e1b88190b0620f4c4f03bc7d completed March 30, 2026, 9:20 p.m.
Created at: March 30, 2026, 4:56 p.m.