Triple
T9289004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AIM Rules for Nominated Advisers |
E223468
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | London Stock Exchange regulation |
C27142
|
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: London Stock Exchange regulation Context triple: [AIM Rules for Nominated Advisers, instanceOf, London Stock Exchange regulation]
-
A.
market segment of the London Stock Exchange
A market segment of the London Stock Exchange is a defined subdivision of the exchange that groups securities with similar characteristics, regulatory requirements, and trading rules to facilitate organized listing and trading.
-
B.
sub-market of the London Stock Exchange
A sub-market of the London Stock Exchange is a distinct segment within the broader exchange that groups companies or securities based on specific criteria such as size, sector, regulatory requirements, or listing standards.
-
C.
stock exchange
A stock exchange is an organized marketplace where securities such as stocks and bonds are listed, bought, and sold under regulated rules and procedures.
-
D.
stock exchange operator
A stock exchange operator is an entity that manages and oversees the trading platform where securities are listed, bought, and sold, ensuring fair, orderly, and transparent market operations.
-
E.
Dutch stock market index
A Dutch stock market index is a statistical measure that tracks the performance of a selected group of publicly traded companies listed on stock exchanges in the Netherlands, reflecting the overall health and trends of the Dutch equity market.
- 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.