Triple
T8287317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hardware and Sound |
E193814
|
entity |
| Predicate | menuPath |
P82539
|
FINISHED |
| Object | Control Panel > Hardware and Sound |
—
|
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: Control Panel > Hardware and Sound | Statement: [Hardware and Sound, menuPath, Control Panel > Hardware and Sound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: menuPath Context triple: [Hardware and Sound, menuPath, Control Panel > Hardware and Sound]
-
A.
menuCategory
Indicates the classification relationship that assigns an item to a specific section or category within a menu.
-
B.
navigationFrom
Indicates a directional navigation relationship where movement or guidance starts from a specified source location or point.
-
C.
navigationRightType
Indicates the type or category of a right or permission related to navigation or movement in a given context.
-
D.
navigationType
Indicates the method or mode by which movement or traversal is carried out between locations or through an environment.
-
E.
hasMenuItem
Indicates that one entity (typically a menu or menu section) includes or offers another entity as one of its menu items.
- F. None of above. chosen
Provenance (4 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7ad4b2008190ad1624e1335147c6 |
completed | March 31, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69cb70ad9fc081908741f8c4a4141edf |
completed | March 31, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:52 p.m.