Triple
T27798579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DirectQuery |
E702180
|
entity |
| Predicate | typicalDataSources |
P75726
|
FINISHED |
| Object | SQL Server |
—
|
NE NERFINISHED |
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: SQL Server | Statement: [DirectQuery, typicalDataSources, SQL Server]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDataSources Context triple: [DirectQuery, typicalDataSources, SQL Server]
-
A.
commonSources
Indicates that two or more entities share the same origin, cause, or source.
-
B.
mainSourceType
chosen
Indicates the primary category or kind of source from which something originates or is derived.
-
C.
dataAcquisition
Indicates the process by which one entity obtains, collects, or retrieves data from another source or system.
-
D.
dataStandard
Indicates that there is a defined, agreed-upon specification or convention governing how the related data is structured, formatted, or exchanged.
-
E.
dataTypes
Indicates that one entity specifies or defines the kinds or formats of data that are valid or expected for 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_6a0017dd31d08190aa5e9f72df83733a |
completed | May 10, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_6a0015a1deb88190b9cdaa60455b0a33 |
completed | May 10, 2026, 5:20 a.m. |
Created at: April 27, 2026, 5:32 p.m.