Triple
T11655477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SQL Server Management Data Warehouse |
E277002
|
entity |
| Predicate | defaultDatabaseName |
P66254
|
FINISHED |
| Object | mdw |
—
|
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: mdw | Statement: [SQL Server Management Data Warehouse, defaultDatabaseName, mdw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultDatabaseName Context triple: [SQL Server Management Data Warehouse, defaultDatabaseName, mdw]
-
A.
primaryDatabase
Indicates that one database serves as the main or authoritative data source in relation to another system or database.
-
B.
primaryDatabaseFormat
Indicates the main data storage format or structure used by a database as its default or principal representation.
-
C.
defaultNameValue
chosen
Indicates that an entity is assigned a standard or fallback name value used when no specific name has been provided.
-
D.
hasDatabase
Indicates that an entity possesses, uses, or is associated with a specific database.
-
E.
databaseType
Indicates the specific kind or category of database technology associated with an 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3cee010819089cffdbefe5a6efb |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.