Triple
T29547490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fast User Switching |
E749667
|
entity |
| Predicate | switchMethod |
P167015
|
FINISHED |
| Object | menu bar selection |
—
|
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: menu bar selection | Statement: [Fast User Switching, switchMethod, menu bar selection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: switchMethod Context triple: [Fast User Switching, switchMethod, menu bar selection]
-
A.
switchType
Indicates that one entity functions as a specific type or category of switch in relation to another entity.
-
B.
switching
Indicates changing from one state, option, or entity to another, replacing the original with a different one.
-
C.
switchOnBy
Indicates that an entity is turned on or activated as the result of an action performed by another entity.
-
D.
switchesPlacesWith
Indicates that two entities exchange their respective positions or roles with each other.
-
E.
codeSwitchedTo
Indicates that an entity has changed from using one language or code system to another within a given context or interaction.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66cf471d88190af960f2c9959878e |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6642e676c8190af0e6b1416eed6d2 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 28, 2026, 5:09 p.m.