Triple
T18645169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OMX Nordic Financials |
E455785
|
entity |
| Predicate | includesCompanyTypes |
P132853
|
FINISHED |
| Object | banks |
—
|
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: banks | Statement: [OMX Nordic Financials, includesCompanyTypes, banks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCompanyTypes Context triple: [OMX Nordic Financials, includesCompanyTypes, banks]
-
A.
includesCompaniesFrom
Indicates that a collection, group, or set contains or incorporates one or more companies as its members or elements.
-
B.
belongsToCompanyType
Indicates that an entity is associated with or classified under a particular type or category of company.
-
C.
representsCompanyType
Indicates that an entity is associated with or classified under a specific type or category of company.
-
D.
underlyingCompanyType
Indicates the classification or category of company that forms the basis or source for another related entity or instrument.
-
E.
relatedCompanyType
Indicates the type or nature of the relationship that one company has to another company.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5500d69648190800da65de0c191b8 |
completed | April 19, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:47 a.m.