Triple
T37657192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SQL Server Data Quality Services |
E937631
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | data quality management feature |
C10343
|
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: data quality management feature Context triple: [SQL Server Data Quality Services, instanceOf, data quality management feature]
-
A.
data quality tool
chosen
A data quality tool is a software solution that profiles, validates, cleans, and monitors data to ensure its accuracy, consistency, completeness, and reliability across systems.
-
B.
quality management tool
A quality management tool is a software system that helps organizations plan, control, monitor, and improve processes and outputs to consistently meet defined quality standards and regulatory requirements.
-
C.
data management tool
A data management tool is a software application that enables users to collect, organize, store, secure, and access data efficiently throughout its lifecycle.
-
D.
data quality law
Data quality law is a conceptual class encompassing the legal principles, regulations, and standards that govern the accuracy, completeness, reliability, and appropriate use of data throughout its lifecycle.
-
E.
data management platform
A data management platform is a centralized system that collects, organizes, governs, and activates data from multiple sources to enable secure, consistent, and analytics-ready information across an organization.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.