Triple

T33433730
Position Surface form Disambiguated ID Type / Status
Subject TextDecoderStream E856194 entity
Predicate errorBehaviorWhenFatalFalse P177026 FINISHED
Object replaces malformed data with U+FFFD 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: replaces malformed data with U+FFFD | Statement: [TextDecoderStream, errorBehaviorWhenFatalFalse, replaces malformed data with U+FFFD]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: errorBehaviorWhenFatalFalse
Context triple: [TextDecoderStream, errorBehaviorWhenFatalFalse, replaces malformed data with U+FFFD]
  • A. failureBehavior
    Indicates how a system, component, or process is expected to respond or act when a failure or error condition occurs.
  • B. isFatalByDefault
    Indicates that the associated condition, action, or event is presumed to result in death unless explicitly specified otherwise.
  • C. errorOn
    Indicates that one entity experiences, produces, or is associated with an error in relation to another entity or context.
  • D. failsWhen
    Indicates that a particular action, process, or condition does not succeed under the specified circumstances or triggers.
  • E. abortModeUsed
    Indicates that an operation, process, or procedure was carried out using an abort or emergency-termination mode.
  • 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_69f349709e7881908c342b4d34f555f4 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6f85bfba48190aba95b40642a8ca7 completed May 3, 2026, 7:25 a.m.
PD Predicate disambiguation batch_69f6f6619404819084662aef1238261c completed May 3, 2026, 7:16 a.m.
PDg Predicate description generation batch_69f6f814fcf48190ae4504154d1b2c05 completed May 3, 2026, 7:24 a.m.
Created at: May 1, 2026, 1:36 a.m.