Triple
T28023564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Group Policy Management Console |
E707750
|
entity |
| Predicate | configurationDomain |
P171778
|
FINISHED |
| Object | computer configuration policies |
—
|
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: computer configuration policies | Statement: [Group Policy Management Console, configurationDomain, computer configuration policies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: configurationDomain Context triple: [Group Policy Management Console, configurationDomain, computer configuration policies]
-
A.
controlDomain
Indicates that one entity has authority over, manages, or regulates the scope, behavior, or operations of another entity or system.
-
B.
implementationDomain
Indicates the domain, field, or context within which something is implemented or put into practical use.
-
C.
outputDomain
Indicates the type or range of values that can be produced as the result of a function, process, or system.
-
D.
defaultDomain
Indicates that one entity serves as the standard or primary domain associated with another entity, used when no more specific domain is specified.
-
E.
transportDomain
Indicates a relationship where an entity operates or functions within the domain or context of transportation activities or systems.
- 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_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a28b8ea881908733485374771c51 |
completed | May 3, 2026, 1:19 a.m. |
Created at: April 27, 2026, 8:11 p.m.