Triple
T7112152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shepard–Byrd Act |
E165730
|
entity |
| Predicate | typeOfOffenseCovered |
P67290
|
FINISHED |
| Object | violent crime |
—
|
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: violent crime | Statement: [Shepard–Byrd Act, typeOfOffenseCovered, violent crime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfOffenseCovered Context triple: [Shepard–Byrd Act, typeOfOffenseCovered, violent crime]
-
A.
includesOffenseType
chosen
Indicates that one entity contains, specifies, or is associated with a particular category or type of offense.
-
B.
targetOffenderType
Indicates the specific category or type of offender that an action, rule, or condition is directed toward.
-
C.
definesOffence
Indicates that one entity specifies or establishes the nature, elements, or scope of an offence associated with another entity.
-
D.
typeOfDiscriminationCovered
Indicates that a particular kind or category of discriminatory behavior is included within the scope of protections, rules, or analysis.
-
E.
accusationType
Indicates the specific category or nature of an accusation made by one party against another.
- 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_69c6888120f081908f8f01b201dc4a4c |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5edf89c8190a069b35ff7768165 |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c4f9788190830288d00cc37026 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.