Triple
T28619279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IDXGIAdapter |
E724340
|
entity |
| Predicate | returnsDescriptionVia |
P90392
|
FINISHED |
| Object | DXGI_ADAPTER_DESC |
—
|
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: DXGI_ADAPTER_DESC | Statement: [IDXGIAdapter, returnsDescriptionVia, DXGI_ADAPTER_DESC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnsDescriptionVia Context triple: [IDXGIAdapter, returnsDescriptionVia, DXGI_ADAPTER_DESC]
-
A.
returnDescription
Indicates that an entity provides or yields a description or explanatory information about something.
-
B.
returnsFor
Indicates that an entity goes back to a previous place, state, or counterpart, typically reversing or completing an earlier departure or action.
-
C.
returnsAs
Indicates that one entity goes back to or resumes a previous state, location, role, or condition associated with another entity.
-
D.
outputDescription
chosen
Indicates that an entity produces or generates a particular description as its output.
-
E.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 28, 2026, 4:32 a.m.