Triple

T15369092
Position Surface form Disambiguated ID Type / Status
Subject governor of Fort Prince of Wales E367494 entity
Predicate instanceOf P0 FINISHED
Object Hudson’s Bay Company position C13313 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: Hudson’s Bay Company position
Context triple: [governor of Fort Prince of Wales, instanceOf, Hudson’s Bay Company position]
  • A. Hudson's Bay Company employee chosen
    A Hudson's Bay Company employee is an individual who works for the historic Canadian retail and former fur-trading enterprise, performing roles that support its commercial, logistical, and administrative operations.
  • B. symbol of Hudson's Bay Company
    A symbol of Hudson's Bay Company represents the historic fur-trading enterprise’s identity and heritage through distinctive visual elements such as its coat of arms, crest, or corporate logo.
  • C. Inuit-owned co-operative
    An Inuit-owned co-operative is a collectively owned and democratically controlled business enterprise established by Inuit community members to provide goods, services, and economic benefits that align with their cultural values and local needs.
  • D. Alaska Native regional corporation
    An Alaska Native regional corporation is a for-profit entity established under the Alaska Native Claims Settlement Act to manage land, financial assets, and business interests on behalf of Alaska Native shareholders within a specific geographic region.
  • E. fur trading post
    A fur trading post is a remote commercial outpost where trappers, Indigenous peoples, and traders exchanged animal pelts for goods such as tools, weapons, textiles, and provisions.
  • 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_69d85a1483788190ad93c2748e8af34b completed April 10, 2026, 2:01 a.m.
Created at: April 10, 2026, 3:18 a.m.