Triple
T3550622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LexisNexis |
E75102
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | information services provider |
C13324
|
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 services provider Context triple: [LexisNexis, instanceOf, information services provider]
-
A.
information system
An information system is an organized combination of people, processes, data, and technology designed to collect, process, store, and distribute information to support decision-making and control in an organization.
-
B.
information resource
An information resource is any identifiable source that stores, provides, or transmits data, knowledge, or content in a form that can be accessed, interpreted, and used by humans or systems.
-
C.
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.
-
D.
information and communications technology hub
An information and communications technology hub is a centralized environment—physical, virtual, or hybrid—where ICT infrastructure, services, expertise, and innovation converge to support connectivity, digital operations, and technological development for organizations and communities.
-
E.
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.
- F. None of above. chosen
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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:20 p.m.