Triple
T34101052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Card, Moran, and Newell keystroke-level model |
E874569
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | GOMS family model |
C58732
|
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: GOMS family model Context triple: [Card, Moran, and Newell keystroke-level model, instanceOf, GOMS family 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.
joint planning and execution system
A joint planning and execution system is an integrated framework that enables multiple agents or stakeholders to collaboratively create, coordinate, and carry out shared plans toward common goals in dynamic environments.
-
C.
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.
-
D.
public services performance study
A public services performance study systematically evaluates the efficiency, effectiveness, equity, and quality of government or publicly funded services to inform improvements in policy and practice.
-
E.
human factors research laboratory
A human factors research laboratory is a specialized facility where researchers study how people interact with systems, products, and environments to optimize safety, performance, and user experience.
- 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.