Triple
T26105308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenCL C 2.0 |
E658519
|
entity |
| Predicate | definesBuiltin |
P23699
|
FINISHED |
| Object | work-group collective built-in functions |
—
|
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: work-group collective built-in functions | Statement: [OpenCL C 2.0, definesBuiltin, work-group collective built-in functions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesBuiltin Context triple: [OpenCL C 2.0, definesBuiltin, work-group collective built-in functions]
-
A.
builtIn
Indicates that one entity is inherently included as a standard, pre-existing component or feature of another entity, rather than being added or installed separately.
-
B.
setBuiltIn
Indicates that a built-in or default configuration, feature, or behavior has been established or enabled for a given entity.
-
C.
definedVia
Indicates that one entity is specified, characterized, or given its meaning by reference to another entity or construct.
-
D.
areDefinedIn
chosen
Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
-
E.
definesFunAs
Indicates that one entity specifies or establishes the meaning, behavior, or implementation of a function for another entity.
- 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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 26, 2026, 7:58 p.m.