Triple
T36635959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sSET Index |
E904463
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Thai stock market index |
C63663
|
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: Thai stock market index Context triple: [sSET Index, instanceOf, Thai stock market index]
-
A.
Thai stock index
chosen
A Thai stock index is a statistical measure that tracks the performance of a selected group of publicly traded companies listed on Thailand’s stock exchange, reflecting the overall movement and health of the Thai equity market.
-
B.
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.
-
C.
Swedish stock market index
A Swedish stock market index is a statistical measure that tracks the performance of a selected group of publicly traded companies listed on Swedish stock exchanges, reflecting the overall movement and health of Sweden’s equity market.
-
D.
Japanese stock market index
A Japanese stock market index is a statistical measure that tracks the performance of a selected group of publicly traded Japanese companies’ stocks to represent the overall movement of Japan’s equity market or specific segments of it.
-
E.
Turkish stock index
A Turkish stock index is a composite measure that tracks the performance of a selected group of publicly traded companies listed on stock exchanges in Turkey, typically used to gauge the overall health and trends of the Turkish equity market.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:11 p.m.