Triple
T33869752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CanvasPattern |
E868166
|
entity |
| Predicate | setTransformArgumentType |
P147322
|
FINISHED |
| Object | DOMMatrix2DInit |
—
|
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: DOMMatrix2DInit | Statement: [CanvasPattern, setTransformArgumentType, DOMMatrix2DInit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setTransformArgumentType Context triple: [CanvasPattern, setTransformArgumentType, DOMMatrix2DInit]
-
A.
transformType
Indicates that one entity is converted or changed from its original form into another specified type or form.
-
B.
argumentType
Indicates that one entity serves as a specific semantic or syntactic argument role (such as subject, object, or complement) in relation to another entity or event.
-
C.
hasArgumentType
chosen
Indicates that an argument or parameter in a function, method, or relation is of a specified data type or class.
-
D.
settingOfTransformation
Indicates the place, context, or environment in which a transformation of an entity or state occurs.
-
E.
transferFunctionType
Indicates the specific kind or category of transfer function that characterizes how input signals are transformed into output signals in a system.
- 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_69f34995029081909ede0f7df73d1a5e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f700a6ff548190b98829c0a623b75f |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5a4f7881909324eb3c20ca96f1 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.