Triple
T28023610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Group Policy Editor |
E707751
|
entity |
| Predicate | policySubcategories |
P168960
|
FINISHED |
| Object | Software Settings |
—
|
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: Software Settings | Statement: [Local Group Policy Editor, policySubcategories, Software Settings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policySubcategories Context triple: [Local Group Policy Editor, policySubcategories, Software Settings]
-
A.
policyCategory
Indicates the classification or type of policy under which an item, rule, or action is grouped.
-
B.
policyTopic
Indicates that one entity is about, concerned with, or categorized under a particular policy-related subject or theme.
-
C.
policyFocus
Indicates that an entity (such as a person, organization, or document) is primarily concerned with, directed toward, or centered on a particular policy area or issue.
-
D.
commonPolicyArea
Indicates that two entities share the same policy domain, topic, or area of regulatory or legislative focus.
-
E.
policyConcept
Indicates that one entity is a policy and the other is a conceptual element or idea that defines, characterizes, or underlies that policy.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f67866e9248190b7ba218f9ca2ae8d |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 27, 2026, 8:11 p.m.