Triple
T8287033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows Registry |
E193808
|
entity |
| Predicate | locationOnDisk |
P76038
|
FINISHED |
| Object | %SystemRoot%\System32\config (for system hives) |
—
|
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: %SystemRoot%\System32\config (for system hives) | Statement: [Windows Registry, locationOnDisk, %SystemRoot%\System32\config (for system hives)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOnDisk Context triple: [Windows Registry, locationOnDisk, %SystemRoot%\System32\config (for system hives)]
-
A.
locationInSystem
Indicates that one entity is situated within or belongs to the spatial or organizational bounds of a particular system.
-
B.
mountingLocation
Indicates the physical position or surface on which something is attached, fixed, or installed.
-
C.
locatedUnder
Indicates that one entity is positioned directly or generally beneath another entity in space.
-
D.
repositoryLocation
Indicates the place or storage context where a repository is hosted, stored, or maintained.
-
E.
objectLocation
chosen
Indicates that one entity is located at, in, or on another entity or spatial region.
- 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_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. |
Created at: March 30, 2026, 5:52 p.m.