Triple

T4667903
Position Surface form Disambiguated ID Type / Status
Subject Heaviside step function E102892 entity
Predicate discontinuousAt P58730 FINISHED
Object x=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: x=0 | Statement: [Heaviside step function, discontinuousAt, x=0]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: discontinuousAt
Context triple: [Heaviside step function, discontinuousAt, x=0]
  • A. disruptsContinuityOf
    Indicates that one entity interrupts, breaks, or otherwise prevents the ongoing, uninterrupted progression or sequence of another entity or process.
  • B. divergesAt
    Indicates that a process, function, or behavior fails to converge or terminate at a specific point or under specific conditions.
  • C. discontinuedIn
    Indicates that an item, product, or service stopped being produced, offered, or supported starting in a specified time or place.
  • D. hasInflectionPointsAt
    Indicates that a function or curve has inflection points located at the specified positions or values.
  • E. discretizes
    Indicates that one entity converts or partitions another entity into a finite set of discrete parts, intervals, or categories.
  • F. None of above. chosen

Provenance (4 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_69bd43d9cba4819086c1ab1c2d9d2133 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd655aceb081908100ffc0498fe183 completed March 20, 2026, 3:18 p.m.
PD Predicate disambiguation batch_69bd6215864c8190b50ba0f63ba87d0c completed March 20, 2026, 3:04 p.m.
PDg Predicate description generation batch_69bd655719dc8190beb6942f343a0ae7 completed March 20, 2026, 3:18 p.m.
Created at: March 20, 2026, 1:15 p.m.