Triple
T6408728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OASIS |
E127653
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | technical consortium |
C8843
|
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: technical consortium Context triple: [OASIS, instanceOf, technical consortium]
-
A.
business consortium
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.
-
B.
technology alliance
chosen
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.
-
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.
private consortium
A private consortium is a collaborative alliance of independent, typically private-sector organizations that pool resources, expertise, and decision-making authority to pursue shared objectives while remaining legally distinct entities.
-
E.
technical subcommittee
A technical subcommittee is a specialized group within a larger organization tasked with analyzing, developing, and recommending solutions on specific technical issues or standards.
- 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_69c0083723d88190b1e37b19df162c08 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 4:41 p.m.