Triple
T28327935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shanghai Stock Exchange listing rules |
E717461
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | stock exchange listing rules |
C27173
|
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: stock exchange listing rules Context triple: [Shanghai Stock Exchange listing rules, instanceOf, stock exchange listing rules]
-
A.
stock market listing
chosen
A stock market listing represents the inclusion of a company's securities on a public exchange, enabling them to be traded by investors under defined regulatory and disclosure requirements.
-
B.
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.
-
C.
regulatory listing
A regulatory listing is an official record or catalog entry of entities, products, or activities that meet specified regulatory requirements and are recognized or authorized by a governing body.
-
D.
London Stock Exchange regulation
London Stock Exchange regulation encompasses the rules, standards, and oversight mechanisms governing the admission, trading, disclosure, and conduct of securities and market participants on the London Stock Exchange to ensure fair, orderly, and transparent markets.
-
E.
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.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 12:29 a.m.