Triple
T6042464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ReLU |
E134578
|
entity |
| Predicate | nonDifferentiableAt |
P68345
|
FINISHED |
| Object | 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: 0 | Statement: [ReLU, nonDifferentiableAt, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonDifferentiableAt Context triple: [ReLU, nonDifferentiableAt, 0]
-
A.
discontinuousAt
Indicates that a function or relation fails to be continuous at a specific point, exhibiting a break, jump, or undefined behavior there.
-
B.
hasInflectionPointsAt
Indicates that a function or curve has inflection points located at the specified positions or values.
-
C.
notFunction
Indicates that the specified entity does not serve as a function or is not used in a functional role within the given context.
-
D.
divergesAt
Indicates that a process, function, or behavior fails to converge or terminate at a specific point or under specific conditions.
-
E.
typeOfDiscontinuity
Indicates the specific kind or category of discontinuity that characterizes a break or interruption in a function, process, or sequence.
- 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_69c00876a69881908088a2626d3b2666 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056e108fc81908775d176ff960fad |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049eb52a08190ac10fd703735f5aa |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8d4a148190bd8f95caae978e1b |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:08 p.m.