Triple

T32415547
Position Surface form Disambiguated ID Type / Status
Subject Kusto Query Language E828323 entity
Predicate dataModelSupport P174054 FINISHED
Object structured data 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: structured data | Statement: [Kusto Query Language, dataModelSupport, structured data]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: dataModelSupport
Context triple: [Kusto Query Language, dataModelSupport, structured data]
  • A. dataModel
    Indicates a relationship where an entity defines, uses, or is structured according to a specific data model or schema.
  • B. dataAccessModel
    Indicates the framework or scheme that governs how data can be accessed, including who can retrieve it, under what conditions, and through which mechanisms.
  • C. supportsModelingOf
    Indicates that one entity provides the capability or functionality needed to represent, simulate, or model another entity or process.
  • D. dataModelLanguage
    Indicates that one entity is a language or formalism used to define, describe, or structure the data model of another entity.
  • E. dataSupports
    Indicates that one piece of data provides evidence, justification, or backing for the validity or reliability of another piece of data, claim, or conclusion.
  • F. None of above. chosen

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_69f6c27c4a9081909dff89529e04cf52 completed May 3, 2026, 3:35 a.m.
PD Predicate disambiguation batch_69f6ba6eb32c8190bf405b2011fa48f7 completed May 3, 2026, 3:01 a.m.
PDg Predicate description generation batch_69f6bb344bb48190a8089f29c0063ded completed May 3, 2026, 3:04 a.m.
Created at: May 1, 2026, 12:54 a.m.