Triple
T33944305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ChiNext board |
E870249
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sub-market of Shenzhen Stock Exchange |
C61532
|
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: sub-market of Shenzhen Stock Exchange Context triple: [ChiNext board, instanceOf, sub-market of Shenzhen Stock Exchange]
-
A.
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.
-
B.
board of the Hong Kong Stock Exchange
The board of the Hong Kong Stock Exchange is the governing body responsible for overseeing the exchange’s strategic direction, regulatory compliance, corporate governance, and overall management to ensure fair, orderly, and efficient market operations.
-
C.
Chinese stock market index
A Chinese stock market index is a statistical measure that tracks the performance of a selected group of publicly traded Chinese companies’ stocks, reflecting overall market or sector-specific trends in China’s equity markets.
-
D.
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.
-
E.
district of Shenzhen
A district of Shenzhen is an administrative subdivision of the city that manages local governance, public services, and development within its designated geographic area.
- 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:49 a.m.