Triple
T4279767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BI Engine |
E97119
|
entity |
| Predicate | workloadType |
P22769
|
FINISHED |
| Object | read-intensive analytical workloads |
—
|
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: read-intensive analytical workloads | Statement: [BI Engine, workloadType, read-intensive analytical workloads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workloadType Context triple: [BI Engine, workloadType, read-intensive analytical workloads]
-
A.
supportsWorkloadType
chosen
Indicates that one entity is capable of handling, operating with, or being compatible with a specified type of workload.
-
B.
typeOfWork
Indicates the kind or category of work associated with or performed by an entity.
-
C.
multitaskingType
Indicates the specific way in which multiple tasks or activities are performed or managed concurrently in a given context.
-
D.
typeOfApplication
Indicates the specific category or kind of application involved in the relationship or action.
-
E.
deploymentType
Indicates the manner or configuration in which a system, application, or component is deployed or made operational.
- 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_69b34544be3c819084d1ab82d29f90c5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b350367da48190b735deef9b5d2d2e |
completed | March 12, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69b347fc4c0c8190a7fcd814e27308a5 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.