Triple
T8022381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Group Policy |
E186767
|
entity |
| Predicate | appliesVia |
P80622
|
FINISHED |
| Object | Group Policy processing engine |
—
|
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: Group Policy processing engine | Statement: [Group Policy, appliesVia, Group Policy processing engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesVia Context triple: [Group Policy, appliesVia, Group Policy processing engine]
-
A.
appliesFrom
Indicates that a rule, condition, or effect begins to be applicable starting from a specific point in time or state.
-
B.
appliesAt
Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
-
C.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
D.
appliesAlsoTo
Indicates that a condition, rule, or characteristic that applies to one entity is additionally applicable to another entity.
-
E.
appliedAs
Indicates that one entity submitted itself or was put forward for consideration in a particular role, position, or context relative to another entity.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3e8eab9c81908098e6b17957316c |
completed | March 31, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:21 p.m.