Triple
T8022385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Group Policy |
E186767
|
entity |
| Predicate | defaultRefreshInterval |
P56156
|
FINISHED |
| Object | 90 minutes |
—
|
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: 90 minutes | Statement: [Group Policy, defaultRefreshInterval, 90 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultRefreshInterval Context triple: [Group Policy, defaultRefreshInterval, 90 minutes]
-
A.
refreshType
Indicates the manner or category of update applied to an entity, such as whether it is a full, partial, or incremental refresh.
-
B.
originalTimeInterval
Indicates the initial or primary time span during which an event, state, or relationship is considered to occur, before any adjustments or derived intervals.
-
C.
latestInterval
Indicates that the related interval is the most recent or last occurring time span among a set of intervals.
-
D.
typicalUpdateFrequency
chosen
Indicates how often an entity is usually updated or refreshed over time.
-
E.
supportsVariableRefreshRate
Indicates that one entity provides compatibility with or functionality for dynamically adjusting refresh rates in coordination with another entity.
- 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_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. |
Created at: March 30, 2026, 5:21 p.m.