Triple

T33433826
Position Surface form Disambiguated ID Type / Status
Subject DecompressionStream E856196 entity
Predicate returnsOnError P174279 FINISHED
Object errored readable stream 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: errored readable stream | Statement: [DecompressionStream, returnsOnError, errored readable stream]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: returnsOnError
Context triple: [DecompressionStream, returnsOnError, errored readable stream]
  • A. viewOnError
    Indicates that an alternative or fallback view is presented when an error occurs during a viewing or rendering process.
  • B. errorOn
    Indicates that one entity experiences, produces, or is associated with an error in relation to another entity or context.
  • C. returnValueOnFailure chosen
    Indicates the value that should be produced or returned when the associated operation or process fails.
  • 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. returnsOnTimeout
    Indicates that a process, function, or operation completes and produces a result automatically when a specified time limit is reached, rather than upon normal completion conditions.
  • 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_69f349709e7881908c342b4d34f555f4 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f7b5ccbda481908fe1945c35e36ce8 completed May 3, 2026, 8:53 p.m.
PD Predicate disambiguation batch_69f7b4c06f5881908f0b98cad6796478 completed May 3, 2026, 8:49 p.m.
Created at: May 1, 2026, 1:36 a.m.