Triple
T696142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 93-205 |
E13897
|
entity |
| Predicate | titleInU.S.Code |
P1119
|
FINISHED |
| Object | 16 U.S.C. §1531 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: 16 U.S.C. §1531 et seq. | Statement: [Public Law 93-205, titleInU.S.Code, 16 U.S.C. §1531 et seq.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleInU.S.Code Context triple: [Public Law 93-205, titleInU.S.Code, 16 U.S.C. §1531 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.
titleNumber
Indicates the numerical designation or sequence number assigned to a title within an ordered set of titles.
-
C.
titles
Indicates that one entity holds a formal title, designation, or name associated with another entity.
-
D.
titleType
Indicates the specific category or kind of title associated with an entity (e.g., whether it is a main title, alternative title, working title, etc.).
-
E.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0c5f51c8190acc4915099e4b384 |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d23e0a08190b08be9d1eff2a1bb |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.