Triple
T7984986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azure Data Factory |
E185663
|
entity |
| Predicate | hasAPI |
P182
|
FINISHED |
| Object | .NET SDK |
E697250
|
NE 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: .NET SDK | Statement: [Azure Data Factory, hasAPI, .NET SDK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: .NET SDK Context triple: [Azure Data Factory, hasAPI, .NET SDK]
-
A.
dotnet/sdk
chosen
dotnet/sdk is the official .NET Software Development Kit that provides the tools, compilers, and libraries needed to build, test, and publish .NET applications.
-
B.
Azure SDKs
Azure SDKs are Microsoft-provided software development kits that enable developers to build, manage, and integrate applications with Azure cloud services across multiple programming languages and platforms.
-
C.
Python SDK
Python SDK is a software development kit that enables developers to build and integrate Python applications with services and platforms such as Azure Data Lake Storage.
-
D.
JavaScript SDK
The JavaScript SDK for Azure Data Lake Storage is a client library that enables developers to programmatically manage and interact with Data Lake Storage resources from JavaScript applications.
-
E.
.NET (via integration)
.NET (via integration) refers to using interoperability tools and middleware to run or connect .NET applications with IBM i systems, enabling .NET-based services to interact with IBM i data and business logic.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca829a2cfc819083d591d58ec04075 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c4a55b881909a96133e56c0dffa |
completed | March 31, 2026, 3:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc567cfe548190bbd163a32c340bcc |
completed | March 31, 2026, 11:19 p.m. |
Created at: March 30, 2026, 5:15 p.m.