Triple
T37456777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infestor |
E930818
|
entity |
| Predicate | unitHotkeyDefault |
P82564
|
FINISHED |
| Object | F (in standard hotkey layout, may vary) |
—
|
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: F (in standard hotkey layout, may vary) | Statement: [Infestor, unitHotkeyDefault, F (in standard hotkey layout, may vary)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unitHotkeyDefault Context triple: [Infestor, unitHotkeyDefault, F (in standard hotkey layout, may vary)]
-
A.
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.
-
B.
keyboardShortcutAlternative
Indicates an alternative keyboard shortcut that can be used to perform the same action or command as another shortcut.
-
C.
unit
Indicates that two quantities are measured using the same standard unit of measurement.
-
D.
controlUnitType
Indicates the specific kind or category of control unit associated with or assigned to an entity.
-
E.
coreUnitType
Indicates that one entity is classified as the primary or fundamental type/category to which another entity (a core unit) belongs.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.