Triple
T17587590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Actian |
E428364
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | data management company |
C32995
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: data management company Context triple: [Actian, instanceOf, data management company]
-
A.
data management body
A data management body is an organized group or authority responsible for establishing, overseeing, and enforcing policies, standards, and practices for the collection, storage, use, and protection of data within an organization or jurisdiction.
-
B.
data management team
A data management team is a group responsible for collecting, organizing, governing, securing, and maintaining an organization’s data to ensure its quality, accessibility, and effective use.
-
C.
Data and AI company
chosen
A Data and AI company specializes in collecting, managing, and analyzing data to build intelligent systems and solutions that automate decisions, generate insights, and create predictive or generative capabilities for businesses.
-
D.
master data management solution
A master data management solution is a centralized platform that defines, consolidates, and governs an organization’s core data entities to ensure consistency, accuracy, and reliability across all systems and business processes.
-
E.
analytics company
An analytics company is an organization that collects, processes, and interprets data to provide insights and recommendations that help clients make informed, data-driven decisions.
- F. None of above.
Provenance (1 batch)
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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:51 a.m.