Triple
T10328485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ReadableStream |
E242819
|
entity |
| Predicate | canErrorWith |
P43799
|
FINISHED |
| Object | stored error state |
—
|
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: stored error state | Statement: [ReadableStream, canErrorWith, stored error state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canErrorWith Context triple: [ReadableStream, canErrorWith, stored error state]
-
A.
failsWhen
Indicates that a particular action, process, or condition does not succeed under the specified circumstances or triggers.
-
B.
errorType
chosen
Indicates the specific category or kind of error associated with an event, action, or entity.
-
C.
failsInGeneralFor
Indicates that an action, method, or approach does not succeed under typical or broad conditions, rather than only in specific edge cases.
-
D.
assertedViolationOf
Indicates that one party has formally claimed or alleged that a rule, law, standard, or obligation has been violated.
-
E.
failsToConformTo
Indicates that one entity does not meet, match, or comply with the standards, rules, or expectations defined by another entity or specification.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7cf21e08190bf605daeea0d9dcf |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:52 a.m.