Triple
T28696596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCSU v GCHQ |
E729432
|
entity |
| Predicate | groundOfReviewDefined |
P103421
|
FINISHED |
| Object | illegality |
—
|
LITERAL FINISHED |
How this triple was built (2 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: illegality | Statement: [CCSU v GCHQ, groundOfReviewDefined, illegality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groundOfReviewDefined Context triple: [CCSU v GCHQ, groundOfReviewDefined, illegality]
-
A.
standardOfReview
Indicates the level and type of scrutiny an authority (such as a court or reviewer) applies when evaluating a prior decision, action, or finding.
-
B.
reviewedFor
chosen
Indicates that one entity has examined or evaluated another entity for a specific purpose, standard, or context.
-
C.
subjectToReviewProcedure
Indicates that an entity is required to undergo a formal review process or procedure before a decision, approval, or action is finalized.
-
D.
reviewedBy
Indicates that an item, work, or action has been examined and evaluated by a specific agent or reviewer.
-
E.
reviewedAs
Indicates that one entity has evaluated, critiqued, or assessed another entity in a particular capacity, role, or context.
- F. None of above.
Provenance (3 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_69f043e6e9688190b6bdd6e5665498ff |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 5:39 a.m.