Triple
T2630714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMD Global |
E59624
|
entity |
| Predicate | marketsIn |
P42354
|
FINISHED |
| Object | global |
—
|
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: global | Statement: [HMD Global, marketsIn, global]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketsIn Context triple: [HMD Global, marketsIn, global]
-
A.
coreMarket
Indicates that an entity serves as the primary or most important market for another entity’s products, services, or activities.
-
B.
market
Indicates the act of promoting, advertising, or selling a product, service, or idea to potential buyers or target audiences.
-
C.
marketStatus
Indicates the current trading or availability condition of an asset, product, or market (e.g., open, closed, active, suspended).
-
D.
marketType
Indicates the classification or category of market in which an entity operates or a transaction occurs (e.g., retail, wholesale, online).
-
E.
relatedMarket
Indicates that two markets are connected or associated, such that activity, conditions, or changes in one market are relevant to or influence the other.
- 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.