Triple
T5777528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WebAssembly.instantiate |
E127480
|
entity |
| Predicate | instantiatesModule |
P66399
|
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, instantiatesModule, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: instantiatesModule Context triple: [WebAssembly.instantiate, instantiatesModule, true]
-
A.
firstModuleLaunch
Indicates the event or relationship where the initial module of a system, project, or mission is launched or activated for the first time.
-
B.
hasModuleConstruct
Indicates that an entity includes, defines, or is composed of a specific module as one of its structural or functional components.
-
C.
includesModuleProvider
Indicates that one entity contains or makes use of another entity that serves as a provider of a specific module or modular functionality.
-
D.
supportsModule
Indicates that one entity provides compatibility, functionality, or resources necessary for another entity’s module to operate or be used.
-
E.
coreModule
Indicates that something functions as a primary or foundational module within a larger system or structure.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69c02ac9603481909e3fa295d7904a15 |
completed | March 22, 2026, 5:45 p.m. |
Created at: March 22, 2026, 3:50 p.m.