Triple
T34100957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GOMS model of human–computer interaction |
E874567
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | human–computer interaction model |
C60529
|
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: human–computer interaction model Context triple: [GOMS model of human–computer interaction, instanceOf, human–computer interaction model]
-
A.
human–computer interaction guideline
A human–computer interaction guideline is a principle or rule that informs the design of interactive systems to make them more usable, efficient, and satisfying for people to use.
-
B.
human-computer interaction literature
Human-computer interaction literature encompasses scholarly and practical works that investigate, design, and evaluate how people perceive, use, and are affected by interactive digital systems and technologies.
-
C.
human–computer interaction tool
A human–computer interaction tool is a software or hardware system designed to facilitate, enhance, or study the ways humans interact with computers through various input, output, and feedback mechanisms.
-
D.
human–computer interaction research center
A human–computer interaction research center is an interdisciplinary organization that studies, designs, and evaluates interactive technologies to improve how people use and experience computer systems.
-
E.
human–computer interaction expert
A human–computer interaction expert is a specialist who studies, designs, and evaluates interactive systems to optimize how people perceive, use, and experience digital technologies.
- F. None of above. chosen
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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:53 a.m.