Triple
T22196852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WebAssembly.Instance |
E548571
|
entity |
| Predicate | exportsContains |
P11236
|
FINISHED |
| Object | exported WebAssembly functions |
—
|
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: exported WebAssembly functions | Statement: [WebAssembly.Instance, exportsContains, exported WebAssembly functions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exportsContains Context triple: [WebAssembly.Instance, exportsContains, exported WebAssembly functions]
-
A.
currentContains
Indicates that one entity presently includes, encloses, or has another entity within its bounds or scope.
-
B.
alsoContains
Indicates that something includes, in addition to its primary contents, another specified element or component.
-
C.
includesElement
chosen
Indicates that one collection, set, or structure contains a specified element as a member or component.
-
D.
containsTest
Indicates that one entity includes or encompasses another entity as a test or testing component.
-
E.
typicallyContain
Indicates that one entity is normally or commonly found within, included in, or held by another entity under usual circumstances.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12ae7c72081909b7817d66391bef4 |
completed | April 28, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:35 p.m.