Triple
T2526648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statute Law (Repeals) Act 1998 |
E56048
|
entity |
| Predicate | typeOfRepealAct |
P2588
|
FINISHED |
| Object | consolidating repeal act |
—
|
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: consolidating repeal act | Statement: [Statute Law (Repeals) Act 1998, typeOfRepealAct, consolidating repeal act]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRepealAct Context triple: [Statute Law (Repeals) Act 1998, typeOfRepealAct, consolidating repeal act]
-
A.
repealed
Indicates that a law, rule, or regulation has been officially revoked or annulled so that it no longer has legal effect.
-
B.
abolishedInEffectBy
Indicates that the legal force or practical operation of something is nullified or terminated as a result of another specified action or measure.
-
C.
typeOfLegislation
chosen
Indicates the specific category or kind of legislation that a given legal act or measure belongs to.
-
D.
repealProcess
Indicates the process by which an existing law, rule, or regulation is formally revoked or annulled.
-
E.
typeOfAmendment
Indicates the specific kind or category of amendment that is being applied to something, such as a document, law, or agreement.
- 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_69ab4a48e4f081908f1218d244608659 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd255f0d081908d20cfb812c4bfc1 |
completed | March 7, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69abd0c2e34c8190a914d5c2afba147c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.