Triple
T370523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toxic Substances Control Act |
E8258
|
entity |
| Predicate | USCodeSections |
P1119
|
FINISHED |
| Object | 15 U.S.C. §2601 et seq. |
—
|
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: 15 U.S.C. §2601 et seq. | Statement: [Toxic Substances Control Act, USCodeSections, 15 U.S.C. §2601 et seq.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USCodeSections Context triple: [Toxic Substances Control Act, USCodeSections, 15 U.S.C. §2601 et seq.]
-
A.
titleOfU.S.Code
chosen
Indicates that a specified title number or name corresponds to a particular section or portion of the United States Code.
-
B.
statutesAtLargeCitation
Indicates that one entity cites or is referenced by a specific citation in the United States Statutes at Large.
-
C.
significantLawSection
Indicates that a particular section of law is especially relevant or important in the context of the described legal situation or relationship.
-
D.
publicLawNumber
Indicates the specific public law identifier associated with a legislative act or statute.
-
E.
constitutionalCitation
Indicates a relationship where one entity cites, references, or is grounded in a specific provision or article of a constitution.
- 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebff472881909fad81d597425ea6 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e960d880819084b3df4e5137a1e2 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.