Triple
T28613833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HKEY_CURRENT_CONFIG |
E724230
|
entity |
| Predicate | typicalSubkey |
P202904
|
FINISHED |
| Object | HKEY_CURRENT_CONFIG\System |
—
|
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: HKEY_CURRENT_CONFIG\System | Statement: [HKEY_CURRENT_CONFIG, typicalSubkey, HKEY_CURRENT_CONFIG\System]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSubkey Context triple: [HKEY_CURRENT_CONFIG, typicalSubkey, HKEY_CURRENT_CONFIG\System]
-
A.
typicalKey
Indicates that the referenced key is the standard or most commonly used key associated with an entity or context.
-
B.
usesSubkeys
Indicates that an entity employs subordinate or derived keys (subkeys) as part of its key management or access mechanism.
-
C.
typicalSubunitOf
Indicates that something is a standard or commonly occurring subcomponent or part of a larger whole.
-
D.
keySubsidiary
Indicates that one organization is the primary or most important subsidiary within a group of related companies.
-
E.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a00cda99c908190980e0bf54cb2e2a4 |
completed | May 10, 2026, 6:25 p.m. |
| PD | Predicate disambiguation | batch_6a00cd1635b08190a791ecfcf87a1d54 |
completed | May 10, 2026, 6:23 p.m. |
| PDg | Predicate description generation | batch_6a00cda8ed348190950ee34bb24ae65b |
completed | May 10, 2026, 6:25 p.m. |
Created at: April 28, 2026, 4:31 a.m.