Triple

T32414525
Position Surface form Disambiguated ID Type / Status
Subject Azure Functions Core Tools E828304 entity
Predicate supportsRuntimeVersion P127933 FINISHED
Object Azure Functions v1 E182240 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 Functions v1 | Statement: [Azure Functions Core Tools, supportsRuntimeVersion, Azure Functions v1]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsRuntimeVersion
Context triple: [Azure Functions Core Tools, supportsRuntimeVersion, Azure Functions v1]
  • A. supportsRuntimeConfiguration
    Indicates that one entity allows its behavior or settings to be adjusted dynamically while the system is running.
  • B. supportsSinceVersion chosen
    Indicates that a given entity has provided support or compatibility for another entity starting from a specified version onward.
  • C. supportsSpecificationVersion
    Indicates that one entity is compatible with and able to operate according to a particular version of a specification.
  • D. requiresLanguageVersion
    Indicates that one entity depends on or must use a specific version of a language in order to function or be considered valid.
  • E. isRuntimeEnforced
    Indicates that a rule, constraint, or condition is actively checked and enforced during program execution rather than at compile time or design time.
  • F. None of above.

Provenance (4 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_6a037c894b488190bcbec2eccaff4a01 completed May 12, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a344f1fd52481908645912dec8d1953 completed June 18, 2026, 8:03 p.m.
PD Predicate disambiguation batch_6a0379edf2d88190b492fca86ed23cac completed May 12, 2026, 7:05 p.m.
Created at: May 1, 2026, 12:53 a.m.