Triple
T28616231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SetEnvironmentVariable |
E724278
|
entity |
| Predicate | returnsNonzeroOn |
P9151
|
FINISHED |
| Object | success |
—
|
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: success | Statement: [SetEnvironmentVariable, returnsNonzeroOn, success]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnsNonzeroOn Context triple: [SetEnvironmentVariable, returnsNonzeroOn, success]
-
A.
isNonzeroFor
chosen
Indicates that a given value, function, or quantity is not equal to zero under specified conditions or for specified inputs.
-
B.
isNonzeroIf
Indicates that one quantity is guaranteed to be nonzero whenever a specified condition or related quantity holds or is nonzero.
-
C.
isNonZeroBecause
Indicates that a value is non-zero specifically due to the stated cause, reason, or contributing factor.
-
D.
returnsOnSuccess
Indicates that an operation or function completes successfully and yields a return value or proceeds to a specified outcome only when no errors occur.
-
E.
returnCondition
Indicates the terms, state, or circumstances under which something that was previously given, lent, or transferred is expected or required to be returned.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 28, 2026, 4:32 a.m.