Triple
T12245724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UK Statutory Instruments |
E291845
|
entity |
| Predicate | scrutinyProcedure |
P8473
|
FINISHED |
| Object | negative resolution procedure |
—
|
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: negative resolution procedure | Statement: [UK Statutory Instruments, scrutinyProcedure, negative resolution procedure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scrutinyProcedure Context triple: [UK Statutory Instruments, scrutinyProcedure, negative resolution procedure]
-
A.
scrutinyMethods
chosen
Indicates the methods or procedures used to examine, inspect, or critically evaluate something.
-
B.
overseesProcedure
Indicates that one entity is responsible for supervising, managing, or directing the execution of a specific procedure performed by another entity.
-
C.
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.
-
D.
supervisionMechanism
Indicates that one entity oversees, monitors, or regulates the actions or behavior of another through a defined control or guidance process.
-
E.
inspectionRequired
Indicates that an entity must undergo an inspection before it can proceed, be used, or be approved.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d38ee10819093ed41d2954bf4ef |
completed | April 10, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69d91c46dcd88190a263db30804bff36 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.