Triple
T6042459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ReLU |
E134578
|
entity |
| Predicate | outputRange |
P28992
|
FINISHED |
| Object | nonnegative real numbers |
—
|
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: nonnegative real numbers | Statement: [ReLU, outputRange, nonnegative real numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outputRange Context triple: [ReLU, outputRange, nonnegative real numbers]
-
A.
rangeOf
chosen
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
B.
designedRange
Indicates the intended or specified range within which something is designed to operate or be effective.
-
C.
operationalRange
Indicates the span of conditions (such as distance, time, or environment) within which a system, device, or process can function effectively and safely.
-
D.
range
Indicates that a value, property, or effect extends between specified limits or over a specified interval or scope.
-
E.
rangeVariant
Indicates that one entity is a variant or alternative form within the value range defined or covered by another entity.
- 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_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. |
Created at: March 22, 2026, 4:08 p.m.