Triple
T18060967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justice and Security Act 2013 |
E432170
|
entity |
| Predicate | typeOfProcedureIntroduced |
P25382
|
FINISHED |
| Object | closed material 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: closed material procedure | Statement: [Justice and Security Act 2013, typeOfProcedureIntroduced, closed material procedure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfProcedureIntroduced Context triple: [Justice and Security Act 2013, typeOfProcedureIntroduced, closed material procedure]
-
A.
typeOfProcedureHandled
Indicates the specific kind or category of procedure that an entity is responsible for managing or processing.
-
B.
typeOfProceedings
chosen
Indicates the specific category or kind of legal or formal process under which an action or case is being conducted.
-
C.
interventionType
Indicates the specific kind or category of action, treatment, or measure applied in an intervention.
-
D.
proceduresDefinedBy
Indicates that certain procedures are specified, established, or authored by a particular entity.
-
E.
overseesProcedure
Indicates that one entity is responsible for supervising, managing, or directing the execution of a specific procedure performed by another entity.
- 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_69d8b9070cac81909fa9473fb1c3f1c7 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4c1066f508190bacf1122e366f87b |
completed | April 19, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:26 a.m.