Triple
T22196874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WebAssembly.Instance |
E548571
|
entity |
| Predicate | prototypeProperty |
P146805
|
FINISHED |
| Object | constructor |
—
|
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: constructor | Statement: [WebAssembly.Instance, prototypeProperty, constructor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prototypeProperty Context triple: [WebAssembly.Instance, prototypeProperty, constructor]
-
A.
modularProperty
Indicates that one entity possesses a characteristic, behavior, or component that is designed to be separable, interchangeable, or recombinable with others in a modular fashion.
-
B.
configurableProperty
Indicates that an entity has a setting or attribute whose value can be adjusted or customized, typically to modify its behavior or characteristics.
-
C.
targetProperty
Indicates that one entity serves as the intended goal, focus, or object of another entity’s action, influence, or effect.
-
D.
providesProperty
Indicates that one entity supplies, grants, or makes a particular property or attribute available to another entity.
-
E.
hasPrototype
Indicates that an entity is based on, derived from, or exemplified by a specific prototype.
- 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_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. |
| PDg | Predicate description generation | batch_69e7222e74248190a2d3671049f117f2 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:35 p.m.