Triple
T8067219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Power BI dataset or model |
E188272
|
entity |
| Predicate | canBeRefreshed |
P17723
|
FINISHED |
| Object | scheduled refresh |
—
|
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: scheduled refresh | Statement: [Power BI dataset or model, canBeRefreshed, scheduled refresh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeRefreshed Context triple: [Power BI dataset or model, canBeRefreshed, scheduled refresh]
-
A.
isReloadable
chosen
Indicates that an entity can be loaded again or refreshed, typically after being used, changed, or depleted.
-
B.
canBeReissued
Indicates that something is eligible to be issued again, such as a document, license, or item that can be re-granted or re-produced after its initial issuance.
-
C.
isUpdatedWhen
Indicates that one entity undergoes a change or refresh whenever another specified entity is modified or updated.
-
D.
isUpdated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or a reference point.
-
E.
refreshType
Indicates the manner or category of update applied to an entity, such as whether it is a full, partial, or incremental refresh.
- 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_69ca82b42674819086840efea12478e5 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ff75d208190b7c53d2fe55878ac |
completed | March 31, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69cb049cd51c8190bb3b0f503e42fa8d |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:26 p.m.