Triple
T31819348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DCUI |
E812218
|
entity |
| Predicate | menuNavigation |
P82539
|
FINISHED |
| Object | keyboard only |
—
|
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: keyboard only | Statement: [DCUI, menuNavigation, keyboard only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: menuNavigation Context triple: [DCUI, menuNavigation, keyboard only]
-
A.
menuType
Indicates the classification or category of a menu (e.g., main menu, context menu, settings menu) associated with an interface or system.
-
B.
menuPath
chosen
Indicates the hierarchical navigation route or sequence of menu items used to access a particular option or function within a menu system.
-
C.
primaryNavigation
Indicates the main navigational relationship or pathway that serves as the primary means of moving between or accessing related entities.
-
D.
navigationFrom
Indicates a directional navigation relationship where movement or guidance starts from a specified source location or point.
-
E.
menuItemType
Indicates the relationship between a menu item and the type or category it belongs to (e.g., appetizer, main course, dessert).
- 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_69f348e97fa48190aa06286962af6dee |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6af7f24a881909e6ae0d937e90ea2 |
completed | May 3, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:45 p.m.