Triple
T32416447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multiple Document Interface |
E828342
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | graphical user interface design pattern |
C57193
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: graphical user interface design pattern Context triple: [Multiple Document Interface, instanceOf, graphical user interface design pattern]
-
A.
graphical user interface feature
A graphical user interface feature is a visual, interactive element (such as buttons, menus, icons, or toolbars) that enables users to perform actions and navigate within a software application.
-
B.
graphical user interface framework
A graphical user interface framework is a collection of tools, libraries, and components that simplifies building, organizing, and managing interactive visual elements of software applications.
-
C.
graphical user interface protocol
A graphical user interface protocol is a defined set of rules and conventions that govern how software components communicate and coordinate to present, manage, and interact with visual elements on a display.
-
D.
operating system user interface element
An operating system user interface element is a visual or interactive component, such as windows, icons, menus, or buttons, that enables users to perceive system state and perform actions within the OS environment.
-
E.
graphical user interface system category
chosen
A graphical user interface system category represents a classification of GUI systems based on shared characteristics such as interaction style, platform, or functional purpose.
- F. None of above.
Provenance (1 batch)
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. |
Created at: May 1, 2026, 12:54 a.m.