Triple

T27612964
Position Surface form Disambiguated ID Type / Status
Subject Microsoft Translator API E700370 entity
Predicate SDKAvailableFor P125228 FINISHED
Object Python 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: Python | Statement: [Microsoft Translator API, SDKAvailableFor, Python]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: SDKAvailableFor
Context triple: [Microsoft Translator API, SDKAvailableFor, Python]
  • A. configurationAvailable
    Indicates that a specific configuration option or setup is present and can be used or applied in the given context.
  • B. hasHardwareCompatibilityWith
    Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
  • C. kitAvailability
    Indicates that a particular kit is available for use, access, or distribution in a given context.
  • D. hasSoftwareCompatibilityWith
    Indicates that one software system can operate correctly and effectively with another software system, without conflicts or required modifications.
  • E. hasSoftwareDevelopmentKit chosen
    Indicates that an entity provides or is associated with a software development kit (SDK) that can be used to develop, integrate, or extend its functionality.
  • 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_69ef6a4f1d9c8190b0705acda054368d completed April 27, 2026, 1:53 p.m.
NER Named-entity recognition batch_69f63894e5848190aec428392562ab06 completed May 2, 2026, 5:47 p.m.
PD Predicate disambiguation batch_69f6370c8c7c8190a02ea82847bb6e76 completed May 2, 2026, 5:40 p.m.
Created at: April 27, 2026, 2:11 p.m.