Triple
T31958613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firearms (Amendment) Act 1988 |
E815972
|
entity |
| Predicate | categoryInUKLaw |
P20156
|
FINISHED |
| Object | public general 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: public general act | Statement: [Firearms (Amendment) Act 1988, categoryInUKLaw, public general act]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: categoryInUKLaw Context triple: [Firearms (Amendment) Act 1988, categoryInUKLaw, public general act]
-
A.
classificationByUK
chosen
Indicates a relationship where an entity is assigned a category, status, or type according to a United Kingdom–specific classification system.
-
B.
juridicalCategory
Indicates the legal classification or status under which an entity or relationship is formally recognized in a juridical system.
-
C.
branchOfLaw
Indicates a relationship where one legal field or discipline is a subdivision or specialized area within a broader body of law.
-
D.
subjectOfLaw
Indicates that a law, legal document, or legal provision is about, concerns, or applies to the referenced subject.
-
E.
typeOfLaw
Indicates that one entity is a specific category or kind of law to which the other entity pertains.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:08 a.m.