Triple
T28023945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ntoskrnl.exe |
E707758
|
entity |
| Predicate | locatedInDefaultPath |
P81264
|
FINISHED |
| Object | C:\Windows\System32 |
—
|
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: C:\Windows\System32 | Statement: [ntoskrnl.exe, locatedInDefaultPath, C:\Windows\System32]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInDefaultPath Context triple: [ntoskrnl.exe, locatedInDefaultPath, C:\Windows\System32]
-
A.
defaultPath
chosen
Indicates that one path among several alternatives is designated as the standard or automatically chosen route in the absence of an explicit selection.
-
B.
builtInLocation
Indicates that one entity is constructed or installed as an integral part within a specific location or structure.
-
C.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
D.
shellLocation
Indicates the physical or logical location where a shell or command-line environment is running or resides.
-
E.
locatedUnder
Indicates that one entity is positioned directly or generally beneath another entity in space.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69ff397e19a88190a945b826159f5290 |
completed | May 9, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69ff392400d0819088d30d08d4a774bd |
completed | May 9, 2026, 1:39 p.m. |
Created at: April 27, 2026, 8:11 p.m.