Triple
T5777527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WebAssembly.instantiate |
E127480
|
entity |
| Predicate | compilesModule |
P29008
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [WebAssembly.instantiate, compilesModule, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compilesModule Context triple: [WebAssembly.instantiate, compilesModule, true]
-
A.
compiledIn
Indicates that a piece of code, program, or module was compiled within or for a specific environment, system, or context.
-
B.
compiledTo
chosen
Indicates that one artifact (such as source code) has been transformed into another, typically lower-level or executable form, through a compilation process.
-
C.
compilesWorkOf
Indicates that one entity gathers, edits, or assembles the works created by another entity into a collection or compilation.
-
D.
compilationType
Indicates the specific method or mode by which something is compiled or assembled into a final form.
-
E.
workCompiledIn
Indicates that a work has been gathered, edited, or assembled into a larger collection, volume, or compilation.
- 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.