Triple
T9288864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AIM |
E223465
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multilateral trading facility |
C27141
|
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: multilateral trading facility Context triple: [AIM, instanceOf, multilateral trading facility]
-
A.
trading consortium
A trading consortium is a collaborative alliance of independent businesses or organizations that pool resources, share information, and coordinate strategies to enhance their collective trading power and market reach.
-
B.
commodities trading hub
A commodities trading hub is a centralized marketplace or platform where buyers and sellers trade physical or financial commodity products, supported by infrastructure, pricing mechanisms, and regulatory frameworks.
-
C.
energy trading software platform
An energy trading software platform is a digital system that enables market participants to analyze prices, manage positions, execute and settle trades, and monitor risk across power, gas, and other energy markets.
-
D.
bilateral trade association
A bilateral trade association is an organization formed between two countries to promote, facilitate, and regulate trade and economic cooperation through agreements, advocacy, and joint initiatives.
-
E.
industry clearing and settlement system
An industry clearing and settlement system is a centralized infrastructure that validates, nets, and finalizes financial transactions between market participants, ensuring accurate, timely, and risk-managed transfer of funds and securities.
- 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:35 p.m.