Triple
T11960478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OMXH |
E284655
|
entity |
| Predicate | underlyingAssets |
P16091
|
FINISHED |
| Object | stocks listed on Nasdaq Helsinki |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: stocks listed on Nasdaq Helsinki | Statement: [OMXH, underlyingAssets, stocks listed on Nasdaq Helsinki]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingAssets Context triple: [OMXH, underlyingAssets, stocks listed on Nasdaq Helsinki]
-
A.
underlyingAsset
chosen
Indicates that one asset serves as the fundamental reference or basis for the value, performance, or contractual terms of another financial instrument or derivative.
-
B.
underlyingConstituentsType
Indicates the type or category of fundamental components that make up or underlie a given entity or structure.
-
C.
underlyingInstrument
Indicates that one financial instrument serves as the reference or basis for the value, payoff, or structure of another financial instrument.
-
D.
tradedAsset
Indicates that an entity is the asset or instrument being exchanged in a trade transaction between parties.
-
E.
assetType
Indicates the specific category or classification of an asset within a broader asset framework or system.
- F. None of above.
Provenance (3 batches)
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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9036941948190b150369094551731 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.