Triple
T28613827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HKEY_CURRENT_CONFIG |
E724230
|
entity |
| Predicate | logicalRootPath |
P128539
|
FINISHED |
| Object | HKEY_CURRENT_CONFIG\ |
—
|
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\ | Statement: [HKEY_CURRENT_CONFIG, logicalRootPath, HKEY_CURRENT_CONFIG\]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: logicalRootPath Context triple: [HKEY_CURRENT_CONFIG, logicalRootPath, HKEY_CURRENT_CONFIG\]
-
A.
logicalPath
Indicates a sequence of logical steps or conditions that connect one entity or state to another within a reasoning or decision process.
-
B.
defaultPath
Indicates that one path among several alternatives is designated as the standard or automatically chosen route in the absence of an explicit selection.
-
C.
namespacePath
chosen
Indicates the hierarchical namespace location or route that defines where an entity is organized within a structured naming system.
-
D.
relatedRoot
Indicates that one entity is connected to another through a shared or common root, origin, or foundational source.
-
E.
rootName
Indicates that the referenced node serves as the primary or top-level root in a hierarchical structure or dependency tree.
- 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_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 4:31 a.m.