Triple
T2630664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nasdaq Helsinki |
E59623
|
entity |
| Predicate | primaryExchangeFor |
P42353
|
FINISHED |
| Object | major Finnish companies |
—
|
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: major Finnish companies | Statement: [Nasdaq Helsinki, primaryExchangeFor, major Finnish companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryExchangeFor Context triple: [Nasdaq Helsinki, primaryExchangeFor, major Finnish companies]
-
A.
primaryExchange
Indicates the main or most significant transfer or trade interaction occurring between two parties or systems.
-
B.
primaryExchangeForDerivatives
Indicates that one entity serves as the main trading venue or marketplace where derivative instruments related to another entity are listed or exchanged.
-
C.
primaryHubFor
Indicates that one entity serves as the main central hub or core point of coordination for another entity or set of entities.
-
D.
baseExchange
Indicates an exchange relationship where one entity serves as the base or reference for converting, trading, or swapping value with another.
-
E.
primaryTerminalFor
Indicates that one entity serves as the main or principal terminal associated with another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69abdb0bf9b881908b239c1310c7bbf3 |
completed | March 7, 2026, 8 a.m. |
Created at: March 6, 2026, 9:50 p.m.