Triple
T35065386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Digital & Integration |
E1011715
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | technology business unit |
C62160
|
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: technology business unit Context triple: [Digital & Integration, instanceOf, technology business unit]
-
A.
technology alliance
A technology alliance is a strategic partnership between organizations that collaborate to develop, share, or integrate technological resources, expertise, and innovations to achieve mutual goals.
-
B.
artificial intelligence business unit
An artificial intelligence business unit is an organizational division dedicated to developing, deploying, and managing AI technologies and strategies to drive innovation, efficiency, and competitive advantage across the enterprise.
-
C.
technology startup
A technology startup is a newly established company that develops innovative tech-based products or services, typically aiming for rapid growth and scalable business models.
-
D.
Alibaba business unit
An Alibaba business unit is a semi-autonomous organizational division within Alibaba Group that focuses on a specific market, product line, or service area, operating with its own strategy, resources, and performance goals while leveraging the group’s shared platforms and infrastructure.
-
E.
technology institution
A technology institution is an organization dedicated to advancing, teaching, and applying technological knowledge through education, research, and innovation.
- 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.