Triple
T35668986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treason Act 1790 |
E1030655
|
entity |
| Predicate | typeOfOffenceRegulated |
P180198
|
FINISHED |
| Object | high treason |
—
|
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: high treason | Statement: [Treason Act 1790, typeOfOffenceRegulated, high treason]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfOffenceRegulated Context triple: [Treason Act 1790, typeOfOffenceRegulated, high treason]
-
A.
typeOfOffenseAddressed
chosen
Indicates the specific category or kind of offense that a given action, measure, or legal provision is intended to address.
-
B.
legalStatusOfOffence
Indicates the legal classification or status assigned to a particular offence (e.g., whether and how it is recognized or treated under law).
-
C.
definesOffence
Indicates that one entity specifies or establishes the nature, elements, or scope of an offence associated with another entity.
-
D.
includesOffenseType
Indicates that one entity contains, specifies, or is associated with a particular category or type of offense.
-
E.
targetOffenderType
Indicates the specific category or type of offender that an action, rule, or condition is directed toward.
- 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a01c51e2d088190b9dcce5b6de1cb9b |
completed | May 11, 2026, 12:01 p.m. |
| PD | Predicate disambiguation | batch_6a01c4c715a48190b7435de8a9d86fd4 |
completed | May 11, 2026, noon |
Created at: May 3, 2026, 4:05 p.m.