Triple
T13922084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Organized Crime Control Act of 1970 |
E334771
|
entity |
| Predicate | createsRemedyType |
P13744
|
FINISHED |
| Object | civil RICO actions |
—
|
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: civil RICO actions | Statement: [Organized Crime Control Act of 1970, createsRemedyType, civil RICO actions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createsRemedyType Context triple: [Organized Crime Control Act of 1970, createsRemedyType, civil RICO actions]
-
A.
creationType
Indicates the manner or process by which something was brought into existence or produced.
-
B.
createdEntityType
Indicates the type or category of entity that was produced or brought into existence as a result of the creation action.
-
C.
remedy
Indicates that one entity serves to cure, alleviate, or counteract a problem, illness, or undesirable condition affecting another entity.
-
D.
createsLawType
Indicates that an entity (such as a legislative body or authority) brings a specific type or category of law into existence.
-
E.
typeOfRemedy
chosen
Indicates that one entity is a specific kind or category of remedy in relation to 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2aa5c1f481908a9d8786872f08fe |
completed | April 14, 2026, 11:53 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.