Triple
T2630684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nasdaq Helsinki |
E59623
|
entity |
| Predicate | hasListingRule |
P2846
|
FINISHED |
| Object | IFRS financial reporting for main market issuers |
—
|
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: IFRS financial reporting for main market issuers | Statement: [Nasdaq Helsinki, hasListingRule, IFRS financial reporting for main market issuers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasListingRule Context triple: [Nasdaq Helsinki, hasListingRule, IFRS financial reporting for main market issuers]
-
A.
hasListingAuthority
Indicates that an entity has the official power or permission to create, approve, or manage listings for another entity or resource.
-
B.
hasRule
chosen
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
C.
isListedBy
Indicates that one entity appears as an item or entry in a list, catalog, or register maintained or provided by another entity.
-
D.
hasListedProductType
Indicates that an entity has a product associated with it that is categorized under a specific listed product type.
-
E.
hasSpecialRules
Indicates that certain entities are governed by additional or exceptional rules that differ from the standard ones.
- 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_69ab4ac8596c8190b34997e73d9e991c |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdb0e7b888190bfa5d2e33f00ec0f |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd810d7f481908e81c305772c4c14 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.