Triple
T19161533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gwichʼin Council International |
E469067
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | permanent participant of the Arctic Council |
C13575
|
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: permanent participant of the Arctic Council Context triple: [Gwichʼin Council International, instanceOf, permanent participant of the Arctic Council]
-
A.
Arctic organization
chosen
An Arctic organization is an entity dedicated to studying, managing, or advocating for the Arctic region’s environment, communities, resources, and geopolitical interests.
-
B.
G7 participant
A G7 participant is a state or entity that takes part in the Group of Seven’s intergovernmental discussions and decision-making processes on global economic, political, and security issues.
-
C.
intergovernmental organization participant
An intergovernmental organization participant is an entity, typically a sovereign state or recognized international body, that formally takes part in the activities, decision-making processes, and governance structures of an intergovernmental organization.
-
D.
G20 participant
A G20 participant is a state or regional organization that takes part in the Group of Twenty’s international economic and financial policy discussions, summits, and cooperative initiatives.
-
E.
Inuit political office
An Inuit political office is a formal position of authority and responsibility within Inuit self-governance or broader governmental structures, representing and advancing the political, social, and cultural interests of Inuit communities.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:06 p.m.