Triple
T34955930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emacs diff-mode |
E1008121
|
entity |
| Predicate | hasKeyBinding |
P191918
|
FINISHED |
| Object | n for next hunk |
—
|
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: n for next hunk | Statement: [Emacs diff-mode, hasKeyBinding, n for next hunk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyBinding Context triple: [Emacs diff-mode, hasKeyBinding, n for next hunk]
-
A.
hasKeyAction
Indicates that an entity performs or is associated with a primary or essential action within a given context.
-
B.
hasKeyEvent
Indicates that an entity includes, is associated with, or is characterized by a significant or defining event.
-
C.
hasKeyState
Indicates that an entity possesses or is associated with a particular key-related status or condition (such as pressed, released, enabled, or disabled).
-
D.
hasKeyboardBy
Indicates that an entity is equipped with or uses a keyboard provided, installed, or controlled by another entity.
-
E.
hasKeyAct
Indicates that one entity possesses or is associated with a primary or central action related to another entity.
- 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69fcef636dfc819085cf91323f2e4edd |
completed | May 7, 2026, 8 p.m. |
Created at: May 3, 2026, 4 p.m.