Triple

T32415145
Position Surface form Disambiguated ID Type / Status
Subject Azure Form Recognizer E828315 entity
Predicate hasSDK P82523 FINISHED
Object Azure Form Recognizer Python SDK
Azure Form Recognizer Python SDK is a client library for Python that enables developers to integrate Azure's AI-powered document analysis and form recognition capabilities into their applications.
E828315 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: Azure Form Recognizer Python SDK | Statement: [Azure Form Recognizer, hasSDK, Azure Form Recognizer Python SDK]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Azure Form Recognizer Python SDK
Triple: [Azure Form Recognizer, hasSDK, Azure Form Recognizer Python SDK]
Generated description
Azure Form Recognizer Python SDK is a client library for Python that enables developers to integrate Azure's AI-powered document analysis and form recognition capabilities into their applications.

Provenance (5 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_69f34919f300819092b541c6277cd68a completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c25bb38881909a5a0552b316e970 completed May 3, 2026, 3:34 a.m.
NED1 Entity disambiguation (via context triple) batch_6a34667086f88190a512bcfc59bfa17b completed June 18, 2026, 9:43 p.m.
NEDg Description generation batch_6a3466e0b1608190a855874e27dde9c4 completed June 18, 2026, 9:45 p.m.
NED2 Entity disambiguation (via description) batch_6a3467911854819088990d7d3c58b74b completed June 18, 2026, 9:48 p.m.
Created at: May 1, 2026, 12:54 a.m.