Triple
T30983944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baugur Group |
E789466
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Icelandic company |
C19447
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Icelandic company Context triple: [Baugur Group, instanceOf, Icelandic company]
-
A.
Icelandic organization
chosen
An Icelandic organization is a formally structured group or entity based in Iceland that coordinates people and resources to pursue specific social, economic, cultural, or governmental objectives within the Icelandic context.
-
B.
Icelandic person
An Icelandic person is an individual who is a native or inhabitant of Iceland, typically characterized by Icelandic citizenship, cultural heritage, and often the Icelandic language.
-
C.
Finnish company
A Finnish company is a business entity established and operating under Finland’s legal, economic, and regulatory framework, typically characterized by strong governance, innovation, and adherence to Nordic business practices.
-
D.
Norwegian company
A Norwegian company is a business entity established and operating under the laws and regulations of Norway, typically registered with the Brønnøysund Register Centre and subject to Norwegian corporate governance, taxation, and reporting requirements.
-
E.
Danish company
A Danish company is a business entity established and operating under the laws of Denmark, typically registered with the Danish Business Authority and subject to Danish corporate, tax, and employment regulations.
- F. None of above.
Provenance (1 batch)
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_69f224c550b081909ddfceb0c3d03bdd |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:55 p.m.