Triple
T37657223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SQL Server Data Quality Services |
E937631
|
entity |
| Predicate | storesKnowledgeIn |
P178523
|
FINISHED |
| Object | DQS_MAIN database |
—
|
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: DQS_MAIN database | Statement: [SQL Server Data Quality Services, storesKnowledgeIn, DQS_MAIN database]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storesKnowledgeIn Context triple: [SQL Server Data Quality Services, storesKnowledgeIn, DQS_MAIN database]
-
A.
knows
Indicates that one entity has knowledge or awareness of another entity or piece of information.
-
B.
usesKnowledgeOf
Indicates that one entity applies or draws upon the knowledge possessed by another entity in performing an action or achieving a result.
-
C.
knowledgeTypeRecorded
chosen
Indicates that the specific type or category of knowledge associated with an entity has been documented or stored.
-
D.
earntBy
Indicates that something (such as money, points, or a reward) is obtained as a result of the actions, work, or performance of a particular entity.
-
E.
usesKnowledgeBase
Indicates that an entity consults or relies on a structured knowledge base as a source of information to perform its actions or make decisions.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:18 p.m.