Triple
T20607830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Enterprise Partnership (Sheffield City Region) |
E506357
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local enterprise partnership |
C11426
|
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: local enterprise partnership Context triple: [Local Enterprise Partnership (Sheffield City Region), instanceOf, local enterprise partnership]
-
A.
business partnership
A business partnership is a formal arrangement in which two or more individuals or entities share ownership, responsibilities, risks, and profits in operating a business.
-
B.
business partner
A business partner is an individual or entity that collaborates with another in a shared commercial venture, jointly contributing resources, sharing risks, and participating in profits and decision-making.
-
C.
regional partnership
chosen
A regional partnership is a collaborative alliance among organizations, governments, or stakeholders within a specific geographic area to coordinate resources, strategies, and initiatives toward shared economic, social, or environmental goals.
-
D.
public sector enterprise
A public sector enterprise is an organization owned and operated by the government to provide goods or services, often with broader social or strategic objectives beyond profit.
-
E.
strategic partnership
A strategic partnership is a long-term, collaborative relationship between two or more independent organizations that align resources, capabilities, and objectives to achieve mutually beneficial competitive advantages they could not easily attain alone.
- 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:41 a.m.