Triple
T32484824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Money Laundering Control Act of 1986 |
E830208
|
entity |
| Predicate | createsSection |
P127277
|
FINISHED |
| Object | 18 U.S.C. § 1956 |
—
|
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: 18 U.S.C. § 1956 | Statement: [Money Laundering Control Act of 1986, createsSection, 18 U.S.C. § 1956]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createsSection Context triple: [Money Laundering Control Act of 1986, createsSection, 18 U.S.C. § 1956]
-
A.
sectionCreates
chosen
Indicates that a particular section is responsible for creating or generating another entity, resource, or content.
-
B.
sectionCreated
Indicates that a new section has been created or added within a larger structure, document, or system.
-
C.
sectionIntroduced
Indicates that a particular section was introduced or added at a specific point in time or context.
-
D.
sectionDefines
Indicates that a specific section formally specifies, describes, or establishes the meaning, rules, or scope of another element or concept.
-
E.
extendedSection
Indicates that one section is a continuation or elaborated extension of another section.
- 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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
Created at: May 1, 2026, 12:58 a.m.