Triple
T27731266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open Software Foundation |
E697435
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | software industry consortium |
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: software industry consortium Context triple: [Open Software Foundation, instanceOf, software industry consortium]
-
A.
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.
-
B.
software engineering organization
A software engineering organization is a structured group of people, processes, and tools dedicated to designing, building, testing, deploying, and maintaining software systems to meet specific business or user needs.
-
C.
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.
-
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.
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.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 3:11 p.m.