Triple
T9627391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Technology Roadmap for Semiconductors |
E232503
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | industry consortium project |
C10923
|
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: industry consortium project Context triple: [International Technology Roadmap for Semiconductors, instanceOf, industry consortium project]
-
A.
industry initiative
An industry initiative is a coordinated effort by organizations within a specific sector to address shared challenges, set standards, or drive collective improvements and innovation.
-
B.
business consortium
chosen
A business consortium is a collaborative association of independent companies that pool resources, expertise, or capital to pursue shared objectives, projects, or market opportunities while retaining their individual autonomy.
-
C.
research consortium
A research consortium is a collaborative alliance of multiple organizations or institutions that pool resources, expertise, and infrastructure to conduct joint research toward shared scientific or technological goals.
-
D.
multinational consortium
A multinational consortium is a collaborative alliance of independent organizations from multiple countries that pool resources, expertise, and risks to pursue shared objectives or large-scale projects.
-
E.
public consortium
A public consortium is a collaborative alliance of multiple public or publicly accountable organizations that pool resources, expertise, and governance to pursue shared goals or projects in the public interest.
- 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_69ca848793ec8190a93a12383a754dc0 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:10 p.m.