Triple
T13019413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TButton |
E322634
|
entity |
| Predicate | defaultActionKey |
P82564
|
FINISHED |
| Object | Enter key |
—
|
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: Enter key | Statement: [TButton, defaultActionKey, Enter key]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultActionKey Context triple: [TButton, defaultActionKey, Enter key]
-
A.
keyAction
Indicates an action that is performed using a key, typically involving locking, unlocking, or otherwise operating a mechanism that requires a key.
-
B.
defaultBehavior
Indicates the standard or fallback way an entity acts or responds when no specific or overriding instructions or conditions are provided.
-
C.
keyboardShortcut
chosen
Indicates that one entity is a keyboard key combination used to trigger or activate the function, command, or action represented by another entity.
-
D.
initialAction
Indicates the first or starting action taken in a sequence of actions or events.
-
E.
defaultOn
Indicates that something is in an enabled or active state by default, without requiring explicit activation.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ecf21bc819082fb512bc479b4be |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:51 p.m.