Triple
T22041177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WebAssembly.CompileError |
E544639
|
entity |
| Predicate | errorDomain |
P121917
|
FINISHED |
| Object | WebAssembly module validation |
—
|
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: WebAssembly module validation | Statement: [WebAssembly.CompileError, errorDomain, WebAssembly module validation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: errorDomain Context triple: [WebAssembly.CompileError, errorDomain, WebAssembly module validation]
-
A.
errorType
Indicates the specific category or kind of error associated with an event, action, or entity.
-
B.
errorSide
Indicates the side, party, or component on which an error occurs or is attributed in a given context.
-
C.
errorTerm
Indicates the specific discrepancy or residual value that quantifies the difference between an observed outcome and its predicted or true value in a model or calculation.
-
D.
errorModel
Indicates the specific model or framework used to represent, quantify, or simulate errors in a process, system, or prediction.
-
E.
affectedDomain
chosen
Indicates the domain, field, or area that is impacted or influenced by a given action, event, or condition.
- 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12828fc788190a22c0e9c2372656b |
completed | April 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:25 p.m.