Triple
T28391047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows Prefetch |
E719155
|
entity |
| Predicate | hasRegistryValue |
P199674
|
FINISHED |
| Object | EnablePrefetcher |
—
|
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: EnablePrefetcher | Statement: [Windows Prefetch, hasRegistryValue, EnablePrefetcher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegistryValue Context triple: [Windows Prefetch, hasRegistryValue, EnablePrefetcher]
-
A.
hasRegistryView
Indicates that an entity has permission or capability to access and view a particular registry or registry-related information.
-
B.
hasValue
Indicates that an entity is associated with a specific numerical, textual, or otherwise defined value.
-
C.
hasRegister
Indicates that one entity possesses, contains, or is associated with a specific register (such as a record, log, or hardware register).
-
D.
hasRegistrar
Indicates that an entity is formally recorded or overseen by a specific registrar organization or authority.
-
E.
hasStandardRegister
Indicates that something is expressed or occurs in a standard, neutral, or non-marked linguistic register.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69ff4fc6077c8190b8fd9b43fcfde986 |
completed | May 9, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69ff4e61fb648190a72f7918961ece9c |
completed | May 9, 2026, 3:10 p.m. |
| PDg | Predicate description generation | batch_69ff4fc5289c819084abd5ede185e96b |
completed | May 9, 2026, 3:16 p.m. |
Created at: April 28, 2026, 1:13 a.m.