Triple
T24660247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan Mayen municipality |
E610516
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Norwegian territorial entity |
C49478
|
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: Norwegian territorial entity Context triple: [Jan Mayen municipality, instanceOf, Norwegian territorial entity]
-
A.
Danish territory
Danish territory is the geographical area under the sovereignty of the Kingdom of Denmark, including continental Denmark, the Faroe Islands, and Greenland, where Danish law and governance apply.
-
B.
former county of Norway
A former county of Norway is an administrative region that previously functioned as a primary subnational division of the country but has since been merged, reorganized, or dissolved through governmental reform.
-
C.
Norwegian organization
A Norwegian organization is an entity based in Norway, such as a company, association, or institution, that is formally structured to pursue specific economic, social, cultural, or public objectives under Norwegian law.
-
D.
region of the Faroe Islands
A region of the Faroe Islands is an administrative or geographical subdivision of the archipelago that groups together nearby islands or municipalities for governance, planning, and statistical purposes.
-
E.
Norwegian foundation
A Norwegian foundation is a legally independent, non-profit entity in Norway that manages assets dedicated to specific public-benefit, charitable, cultural, or private purposes according to a founding document and national regulations.
- F. None of above. chosen
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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
Created at: April 18, 2026, 2:34 a.m.