Triple
T32416547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CWnd |
E828343
|
entity |
| Predicate | hasVirtualFunction |
P173226
|
FINISHED |
| Object | PreCreateWindow |
—
|
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: PreCreateWindow | Statement: [CWnd, hasVirtualFunction, PreCreateWindow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVirtualFunction Context triple: [CWnd, hasVirtualFunction, PreCreateWindow]
-
A.
hasVirtualMethod
chosen
Indicates that a class or type defines a method that is declared as virtual, allowing it to be overridden in derived classes for polymorphic behavior.
-
B.
hasForeignFunctionInterface
Indicates that an entity supports or uses a mechanism to call or interoperate with functions written in a foreign (external) programming language or environment.
-
C.
hasVirtualMachine
Indicates that one entity possesses, contains, or is associated with a virtual machine instance.
-
D.
hasPublicFunction
Indicates that an entity possesses a function or method that is publicly accessible or callable from outside its defining scope.
-
E.
hasFunctionInPresent
Indicates that an entity currently performs, exhibits, or fulfills a specific function or role at the present time.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 1, 2026, 12:54 a.m.