Triple
T1953222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Organising Committee of the Olympic and Paralympic Games |
E42205
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | company limited by guarantee |
C8143
|
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: company limited by guarantee Context triple: [London Organising Committee of the Olympic and Paralympic Games, instanceOf, company limited by guarantee]
-
A.
limited partnership
A limited partnership is a business structure in which at least one general partner manages the business and bears unlimited liability, while one or more limited partners contribute capital and have liability limited to their investment with no role in day-to-day management.
-
B.
government-owned company
A government-owned company is a legal entity engaged in commercial activities that is wholly or majority owned and controlled by a national, regional, or local government.
-
C.
governing council
A governing council is a formal body of appointed or elected individuals responsible for making high-level decisions, setting policies, and providing oversight for an organization, community, or institution.
-
D.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
E.
self-governing organization
A self-governing organization is an entity that independently establishes and enforces its own rules, structures, and decision-making processes without external control.
- 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_69a8870eea088190a38781990812a9bc |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:36 p.m.