Triple
T5777522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WebAssembly.instantiate |
E127480
|
entity |
| Predicate | returnProperty |
P3699
|
FINISHED |
| Object | module |
—
|
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: module | Statement: [WebAssembly.instantiate, returnProperty, module]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnProperty Context triple: [WebAssembly.instantiate, returnProperty, module]
-
A.
returnProphecy
Indicates that an entity gives back or delivers a previously received prophecy to its original source or rightful recipient.
-
B.
returnService
Indicates a relationship where a service that was previously provided is being sent back, reversed, or requested to be undone or refunded.
-
C.
providesProperty
chosen
Indicates that one entity supplies, grants, or makes a particular property or attribute available to another entity.
-
D.
returnedBy
Indicates that something is given, sent, or brought back to a previous sender, owner, or source by another entity.
-
E.
returns
Indicates that one entity gives or sends something back to another entity, often as a result or outcome of a process or action.
- 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.