Triple
T18645013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OMX Copenhagen 20 |
E455781
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Danish stock index |
C40838
|
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: Danish stock index Context triple: [OMX Copenhagen 20, instanceOf, Danish stock index]
-
A.
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.
-
B.
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.
-
C.
Euro Stoxx 50 index
The Euro Stoxx 50 index is a leading stock market index that tracks the performance of 50 large, blue-chip companies from 11 Eurozone countries, representing the euro area's major sectors and markets.
-
D.
German stock index
A German stock index is a statistical measure that tracks the performance of a selected group of publicly traded companies listed on German stock exchanges, typically representing the overall health and trends of Germany’s equity market.
-
E.
German stock market index
A German stock market index is a statistical measure that tracks the performance of a selected group of publicly traded German companies’ shares, reflecting the overall state of Germany’s equity market or specific segments of it.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.