Triple
T37658495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SQL Server Native Client |
E937657
|
entity |
| Predicate | connectionStringProviderName |
P100222
|
FINISHED |
| Object | SQLNCLI |
—
|
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: SQLNCLI | Statement: [SQL Server Native Client, connectionStringProviderName, SQLNCLI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectionStringProviderName Context triple: [SQL Server Native Client, connectionStringProviderName, SQLNCLI]
-
A.
connectionStringKeyword
Indicates that one entity is a keyword or token used within a connection string that defines or configures a connection between systems or components.
-
B.
connectionStringValueExample
chosen
Indicates an example value of a connection string used to define how to connect to a data source or service.
-
C.
namingConnectionType
Indicates a relationship specifying the type or nature of a naming connection that exists between two entities.
-
D.
commonConnectorName
Indicates that two or more entities share the same connector name used to link or interface them.
-
E.
configurationName
Indicates the specific label or identifier assigned to a particular configuration setting or setup.
- 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_69fff9b126b4819085a4cf8791d388d1 |
completed | May 10, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69fff8f913a881908d3b7e490d92631f |
completed | May 10, 2026, 3:18 a.m. |
Created at: May 3, 2026, 4:18 p.m.