Triple

T5777573
Position Surface form Disambiguated ID Type / Status
Subject WebAssembly.compileStreaming E127481 entity
Predicate throwsOn P8788 FINISHED
Object non-OK HTTP status codes in some implementations 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: non-OK HTTP status codes in some implementations | Statement: [WebAssembly.compileStreaming, throwsOn, non-OK HTTP status codes in some implementations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: throwsOn
Context triple: [WebAssembly.compileStreaming, throwsOn, non-OK HTTP status codes in some implementations]
  • A. throws
    Indicates that one entity propels or hurls another entity or object through space, typically by a deliberate physical action.
  • B. throwsStyle
    Indicates that one entity performs a throwing action using a particular style, technique, or manner.
  • C. failsWhen chosen
    Indicates that a particular action, process, or condition does not succeed under the specified circumstances or triggers.
  • D. throwsPosition
    Indicates that one entity performs a throwing action that determines or affects the spatial position of another entity.
  • E. exceptionToOaths
    Indicates that a situation, condition, or rule provides a valid exception to an otherwise binding oath or sworn obligation.
  • 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_69c008361fa88190aefa4dc41b051e7f completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c02acb12c081908e4beee4a957f9f9 completed March 22, 2026, 5:45 p.m.
PD Predicate disambiguation batch_69c021d0c6088190ba670ddcdbf5ca3e completed March 22, 2026, 5:07 p.m.
Created at: March 22, 2026, 3:50 p.m.