Triple
T28613805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HKEY_CURRENT_USER |
E724229
|
entity |
| Predicate | accessPathInRegistryEditor |
P80145
|
FINISHED |
| Object | Computer\HKEY_CURRENT_USER |
—
|
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: Computer\HKEY_CURRENT_USER | Statement: [HKEY_CURRENT_USER, accessPathInRegistryEditor, Computer\HKEY_CURRENT_USER]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessPathInRegistryEditor Context triple: [HKEY_CURRENT_USER, accessPathInRegistryEditor, Computer\HKEY_CURRENT_USER]
-
A.
accessPath
Indicates a path, route, or means by which something can be reached, entered, or accessed.
-
B.
registryKey
Indicates a relationship where a software component or process creates, modifies, or references a specific key within a system’s registry.
-
C.
registryPathPrefix
chosen
Indicates that one entity specifies the leading portion of a registry path under which the other entity’s registry keys or values are located.
-
D.
aliasOfExplorer
Indicates that one entity is an alternative name, nickname, or alias used for a particular explorer.
-
E.
namespacePath
Indicates the hierarchical namespace location or route that defines where an entity is organized within a structured naming system.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 28, 2026, 4:31 a.m.