Triple
T8287061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HKEY_CLASSES_ROOT |
E193809
|
entity |
| Predicate | logicalPath |
P82536
|
FINISHED |
| Object | HKEY_CLASSES_ROOT |
—
|
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_CLASSES_ROOT | Statement: [HKEY_CLASSES_ROOT, logicalPath, HKEY_CLASSES_ROOT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: logicalPath Context triple: [HKEY_CLASSES_ROOT, logicalPath, HKEY_CLASSES_ROOT]
-
A.
lightPath
Indicates the route or trajectory that light follows as it travels between entities or through a medium.
-
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.
ultimatePathTo
Indicates that one entity represents the final, most fundamental, or decisive route, method, or means by which another entity is reached or achieved.
-
D.
binaryLocation
Indicates that one entity is the physical or logical location where another binary or executable artifact resides.
-
E.
locationPattern
Indicates a recurring or structured spatial relationship, where an entity consistently appears or is arranged in a particular type of location or spatial configuration.
- 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7ad4b2008190ad1624e1335147c6 |
completed | March 31, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69cb70ad9fc081908741f8c4a4141edf |
completed | March 31, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:52 p.m.