Triple
T32415589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kusto Query Language |
E828323
|
entity |
| Predicate | typicalDataSource |
P141050
|
FINISHED |
| Object | telemetry 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: telemetry data | Statement: [Kusto Query Language, typicalDataSource, telemetry data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDataSource Context triple: [Kusto Query Language, typicalDataSource, telemetry data]
-
A.
dataSourceFor
Indicates that one entity serves as the origin or provider of data that is used or consumed by another entity.
-
B.
hasSourceOfData
chosen
Indicates that one entity serves as the origin or provider of the data used or referenced by another entity.
-
C.
trainingDataSource
Indicates the origin or provider from which the training data for a model or system is obtained.
-
D.
mainSourceType
Indicates the primary category or kind of source from which something originates or is derived.
-
E.
typicalSourceSoftware
Indicates that one entity is the software program that commonly or characteristically produces or provides the other entity.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:54 a.m.