Triple
T32930968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glasgow Financial Alliance for Net Zero |
E842397
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | private sector alliance |
C12009
|
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: private sector alliance Context triple: [Glasgow Financial Alliance for Net Zero, instanceOf, private sector alliance]
-
A.
public-sector collaboration
Public-sector collaboration is the coordinated effort among government agencies and public institutions, often with private and nonprofit partners, to jointly design, implement, and manage policies or services that address shared societal challenges.
-
B.
public sector enterprise
A public sector enterprise is an organization owned and operated by the government to provide goods or services, often with broader social or strategic objectives beyond profit.
-
C.
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.
-
D.
private consortium
chosen
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.
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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:20 a.m.