Triple
T827301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transport Committee (London Assembly) |
E17882
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | scrutiny committee |
C1999
|
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: scrutiny committee Context triple: [Transport Committee (London Assembly), instanceOf, scrutiny committee]
-
A.
government committee
chosen
A government committee is a formally established group of officials or representatives tasked with studying specific issues, developing recommendations, and overseeing particular areas of public policy or administration.
-
B.
intelligence oversight committee
An intelligence oversight committee is a formal body responsible for monitoring, reviewing, and regulating the activities of intelligence agencies to ensure legality, accountability, and alignment with democratic norms and national interests.
-
C.
standing committee of a state legislature
A standing committee of a state legislature is a permanent, specialized group of legislators that reviews, amends, and recommends action on proposed laws and issues within a specific policy area.
-
D.
board committee
A board committee is a small, specialized group of board members delegated specific responsibilities to support the board’s governance, oversight, and decision-making functions.
-
E.
United States Senate committee
A United States Senate committee is a specialized group of senators assigned to consider legislation, conduct hearings, and oversee federal agencies and programs within a particular policy area.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:38 p.m.