Triple
T19309591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 90-321 |
E482929
|
entity |
| Predicate | codifiedSectionsBegin |
P775
|
FINISHED |
| Object | 15 U.S.C. § 1601 |
—
|
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. § 1601 | Statement: [Public Law 90-321, codifiedSectionsBegin, 15 U.S.C. § 1601]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codifiedSectionsBegin Context triple: [Public Law 90-321, codifiedSectionsBegin, 15 U.S.C. § 1601]
-
A.
codifiedIn
chosen
Indicates that something is formally recorded, defined, or established within a specific document, code, or legal/institutional text.
-
B.
codifiedUnderAuthority
Indicates that something has been formally established, defined, or recorded according to the rules or power of a specific authority.
-
C.
codificationTopicNumber
Indicates the numbered topic or subject under which something is organized or classified in a codification system.
-
D.
governsSectionOf
Indicates that one entity has authoritative control or regulatory oversight over a specific section or part of another entity.
-
E.
legalCodePromulgatedBy
Indicates that a specific legal code was formally issued or enacted by a particular authority or governing body.
- 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e604cc62e08190b5ba5dfc44efdc5c |
completed | April 20, 2026, 10:49 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:32 p.m.