Triple
T37706837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Graph Python SDK |
E939218
|
entity |
| Predicate | supportsAPIVersion |
P127933
|
FINISHED |
| Object | v1.0 |
—
|
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: v1.0 | Statement: [Microsoft Graph Python SDK, supportsAPIVersion, v1.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAPIVersion Context triple: [Microsoft Graph Python SDK, supportsAPIVersion, v1.0]
-
A.
supportsSpecificationVersion
Indicates that one entity is compatible with and able to operate according to a particular version of a specification.
-
B.
supportsSinceVersion
chosen
Indicates that a given entity has provided support or compatibility for another entity starting from a specified version onward.
-
C.
supportsKubernetesVersion
Indicates that one entity is compatible with and able to run or work correctly with a specified Kubernetes version.
-
D.
supportsSince
Indicates that one entity has been providing support to another entity starting from a specific point in time and continuing thereafter.
-
E.
supportsVersioning
Indicates that the subject provides or is compatible with functionality for managing and maintaining multiple versions of an item or resource.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.