Triple
T11958461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open Multi-Processing |
E284609
|
entity |
| Predicate | hasDirectiveSyntax |
P95858
|
FINISHED |
| Object | pragma-based for 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-based for C and C++ | Statement: [Open Multi-Processing, hasDirectiveSyntax, pragma-based for C and C++]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectiveSyntax Context triple: [Open Multi-Processing, hasDirectiveSyntax, pragma-based for C and C++]
-
A.
hasDirective
Indicates that one entity issues, contains, or is governed by a specific directive or instruction associated with another entity.
-
B.
hasSyntaxKeyword
chosen
Indicates that an element or construct is associated with, or marked by, a specific keyword in the syntax of a language or formal system.
-
C.
usesDirective
Indicates that one entity applies, references, or relies on a specific directive issued or defined by another entity.
-
D.
hasSyntaxInfluenceFrom
Indicates that the syntax of one entity is influenced, shaped, or derived from the syntax of another entity.
-
E.
definesSyntax
Indicates that one entity specifies or determines the formal structure, rules, or grammar by which another entity is expressed or interpreted.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903681a00819098c2b5260e2ef834 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.