Triple
T8920171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Power BI REST API |
E212393
|
entity |
| Predicate | managesResourceType |
P86412
|
FINISHED |
| Object | datasets |
—
|
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: datasets | Statement: [Power BI REST API, managesResourceType, datasets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesResourceType Context triple: [Power BI REST API, managesResourceType, datasets]
-
A.
managerType
Indicates the specific category or role classification of a manager within an organizational or system context.
-
B.
classificationTypeManaged
Indicates that the classification type is controlled or administered through a managed process or system rather than being assigned freely or ad hoc.
-
C.
hasTypeOfManagement
Indicates that an entity is associated with or operates under a specified form or style of management.
-
D.
typeOfResourceRegulated
Indicates that one entity specifies the kind or category of resource that is subject to regulation by another entity.
-
E.
registryManaged
Indicates that an entity is controlled, maintained, or overseen by a central registry or registration authority.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc664f099c8190be6d20a4574212ca |
completed | April 1, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
| PDg | Predicate description generation | batch_69cc600a59708190ae426044bbcd7929 |
completed | April 1, 2026, midnight |
Created at: March 30, 2026, 6:56 p.m.