Triple
T2629391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenMP |
E59596
|
entity |
| Predicate | usesDirectiveSyntax |
P30407
|
FINISHED |
| Object | #pragma omp in C and C++ |
—
|
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: #pragma omp in C and C++ | Statement: [OpenMP, usesDirectiveSyntax, #pragma omp in C and C++]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDirectiveSyntax Context triple: [OpenMP, usesDirectiveSyntax, #pragma omp in C and C++]
-
A.
usesDirective
chosen
Indicates that one entity applies, references, or relies on a specific directive issued or defined by another entity.
-
B.
definesSyntax
Indicates that one entity specifies or determines the formal structure, rules, or grammar by which another entity is expressed or interpreted.
-
C.
definesUseOf
Indicates that one entity specifies or determines how another entity is to be used or applied.
-
D.
usesDirectory
Indicates that one entity makes use of or operates within a particular directory in a file system or organizational structure.
-
E.
symbolicallyUses
Indicates that one entity employs another as a symbol or representation to convey meaning, ideas, or associations rather than for its literal or practical function.
- 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_69ab4ac8596c8190b34997e73d9e991c |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdb0e7b888190bfa5d2e33f00ec0f |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd810d7f481908e81c305772c4c14 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.