Triple
T5933893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capgemini |
E131998
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | information technology consulting company |
C16706
|
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: information technology consulting company Context triple: [Capgemini, instanceOf, information technology consulting company]
-
A.
computer services company
A computer services company is an organization that provides technical expertise, support, and solutions related to computer systems, software, networks, and IT infrastructure for individuals or other businesses.
-
B.
information technology agency
An information technology agency is an organization that plans, develops, manages, and supports technology systems and services to meet the digital and operational needs of its clients or stakeholders.
-
C.
information and communications technology organization
chosen
An information and communications technology organization is an entity that develops, manages, or delivers digital and networked technologies, services, and infrastructure to enable electronic communication, data processing, and information exchange.
-
D.
consulting organization
A consulting organization is a professional services entity that provides expert advice, analysis, and solutions to clients to improve their performance, solve specific problems, or achieve strategic objectives.
-
E.
information services provider
An information services provider is an entity that collects, processes, and delivers data, analysis, or knowledge-based content to users or organizations through various digital or physical channels.
- 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_69c0085c55dc8190aa90e242c956e2fa |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 4 p.m.