Triple
T28616113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LoadLibrary |
E724276
|
entity |
| Predicate | definedInHeader |
P179201
|
FINISHED |
| Object | windows.h |
—
|
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: windows.h | Statement: [LoadLibrary, definedInHeader, windows.h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedInHeader Context triple: [LoadLibrary, definedInHeader, windows.h]
-
A.
definesHeader
chosen
Indicates that one entity serves as the header or defining heading for another entity.
-
B.
areDefinedIn
Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
-
C.
definedInPart
Indicates that something is specified, described, or formally established within a particular part or section of a larger whole.
-
D.
definedInField
Indicates that something (such as a concept, method, or element) is formally specified, declared, or established within a particular field, domain, or area of study.
-
E.
definedInModel
Indicates that an element or concept is specified, structured, or formally represented within a particular model.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 28, 2026, 4:32 a.m.