Triple
T28615051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Read-Only Domain Controller |
E724255
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Microsoft Windows Server feature |
C23407
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Microsoft Windows Server feature Context triple: [Read-Only Domain Controller, instanceOf, Microsoft Windows Server feature]
-
A.
Microsoft server role
chosen
A Microsoft server role is a predefined set of software components and services that configure a Windows Server to perform a specific network function, such as web hosting, file sharing, or domain control.
-
B.
Windows component
A Windows component is a modular part of the Microsoft Windows operating system that provides specific functionality or services, such as system utilities, drivers, or user interface elements, which can be installed, configured, or updated independently.
-
C.
Microsoft SQL Server component
A Microsoft SQL Server component is a modular part of the SQL Server ecosystem that provides specific database, analytics, integration, or management functionality within the overall data platform.
-
D.
Microsoft Office feature
A Microsoft Office feature is a specific tool or capability within Office applications that enhances productivity by enabling users to create, edit, analyze, or present information more efficiently.
-
E.
Microsoft developer platform service
A Microsoft developer platform service is a cloud-based or on-premises offering that provides tools, runtimes, APIs, and infrastructure to help developers build, deploy, and manage applications within the Microsoft ecosystem.
- F. None of above.
Provenance (1 batch)
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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:31 a.m.