Triple
T19180319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Intelligence Committee |
E469553
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intelligence committee |
C37895
|
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: intelligence committee Context triple: [Joint Intelligence Committee, instanceOf, intelligence committee]
-
A.
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.
-
B.
intelligence community
The intelligence community is a collective network of government agencies and organizations responsible for gathering, analyzing, and disseminating information to support national security and foreign policy decision-making.
-
C.
government committee
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.
-
D.
interagency committee
chosen
An interagency committee is a collaborative body composed of representatives from multiple government agencies formed to coordinate policies, share information, and address cross-cutting issues.
-
E.
independent committee
An independent committee is a group of individuals formally appointed to make decisions or recommendations autonomously, free from undue influence by interested parties or external authorities.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:07 p.m.