Triple
T33662611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Life Highland |
E862391
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | arms-length external organization |
C47382
|
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: arms-length external organization Context triple: [High Life Highland, instanceOf, arms-length external organization]
-
A.
arms-length external organisation
chosen
An arms-length external organisation is an independent entity that operates separately from, but is funded or overseen by, a parent body (such as a government or corporation) to deliver specific functions or services with reduced direct control.
-
B.
affiliated organization network
An affiliated organization network is a structured system of interconnected organizations that maintain formal relationships to collaborate, share resources, and pursue aligned goals while retaining their individual identities.
-
C.
commercial arm of an intergovernmental organization
The commercial arm of an intergovernmental organization is an operational entity established by member states to conduct revenue-generating business activities that support and advance the organization’s public-policy and developmental objectives.
-
D.
independent organization
An independent organization is an entity that operates autonomously from external control or affiliation, making its own decisions, policies, and governance.
-
E.
Supporting Organization
A Supporting Organization is an entity that exists primarily to provide resources, services, or assistance to another organization in order to help it achieve its goals.
- 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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:42 a.m.