Triple
T4319887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intelligence Services Act 1994 |
E96486
|
entity |
| Predicate | establishesOversightMechanism |
P8878
|
FINISHED |
| Object | Intelligence and Security Committee of Parliament |
E103126
|
NE FINISHED |
How this triple was built (3 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Intelligence and Security Committee of Parliament | Statement: [Intelligence Services Act 1994, establishesOversightMechanism, Intelligence and Security Committee of Parliament]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Intelligence and Security Committee of Parliament Context triple: [Intelligence Services Act 1994, establishesOversightMechanism, Intelligence and Security Committee of Parliament]
-
A.
Intelligence and Security Committee of Parliament
chosen
The Intelligence and Security Committee of Parliament is a cross-party UK parliamentary body that scrutinizes the work, policies, and expenditure of the country’s intelligence and security agencies.
-
B.
Parliamentary Joint Committee on Intelligence and Security
The Parliamentary Joint Committee on Intelligence and Security is an Australian parliamentary oversight body that reviews and monitors the activities, administration, and legislation of the nation’s intelligence and security agencies.
-
C.
Joint Intelligence Committee (United Kingdom)
The Joint Intelligence Committee (United Kingdom) is a high-level governmental body that coordinates, assesses, and advises on national security and intelligence matters for the UK government.
-
D.
National Security and Intelligence Committee of Parliamentarians
The National Security and Intelligence Committee of Parliamentarians is a Canadian multi-party oversight body that reviews and reports on the activities of the country’s national security and intelligence agencies.
-
E.
Intelligence and Security Division
The Intelligence and Security Division is a NATO body responsible for providing strategic intelligence, security policy, and threat assessments to support the Alliance’s political and military decision-making.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishesOversightMechanism Context triple: [Intelligence Services Act 1994, establishesOversightMechanism, Intelligence and Security Committee of Parliament]
-
A.
headOfGovernmentOversight
Indicates that one entity holds primary responsibility for supervising, directing, or managing the governmental activities or operations of another entity.
-
B.
oversightBody
chosen
Indicates that one entity has formal authority to supervise, review, or regulate the actions or decisions of another entity.
-
C.
fundingOversight
Indicates that one entity is responsible for monitoring, regulating, or supervising the use and allocation of funds provided to another entity.
-
D.
oversightConcerns
Indicates that there are worries or issues regarding the adequacy, effectiveness, or appropriateness of supervision, monitoring, or regulatory control over something.
-
E.
oversightFocus
Indicates that one entity’s oversight, supervision, or monitoring activities are specifically directed toward another entity or aspect.
- F. None of above.
Provenance (4 batches)
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_69b345422aac81909ddbadae437d122e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35112ec008190958487f501481887 |
completed | March 12, 2026, 11:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5f5bf4dd48190b84d8488a4f196a8 |
completed | March 14, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69b34f4bec888190987fc2631498b637 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:12 p.m.