Triple
T3505327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Lords Appointments Commission |
E74061
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public appointments commission |
C11671
|
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: public appointments commission Context triple: [House of Lords Appointments Commission, instanceOf, public appointments commission]
-
A.
commission member
A commission member is an individual appointed or elected to serve on a formal committee or board, participating in deliberations, decision-making, and oversight within the commission’s defined scope of authority.
-
B.
commissioners court
A commissioners court is a county-level governing body, typically composed of elected commissioners and a presiding judge or chair, responsible for setting local policies, budgets, and administrative regulations.
-
C.
appointing authority
chosen
An appointing authority is an individual or entity legally empowered to select, hire, promote, or otherwise make official personnel decisions for positions within an organization or governmental body.
-
D.
city commission
A city commission is a governing body, typically composed of elected or appointed officials, responsible for making policy decisions, overseeing municipal services, and guiding the development and administration of a city.
-
E.
technical commission system
A technical commission system is a structured framework of processes, tools, and governance used to plan, execute, verify, and document the commissioning and performance validation of technical systems or facilities.
- 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:18 p.m.