Triple
T1874846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Power Act |
E39119
|
entity |
| Predicate | U.S.CCitation |
P24251
|
FINISHED |
| Object | 16 U.S.C. §§ 791a–828c |
—
|
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. §§ 791a–828c | Statement: [Federal Power Act, U.S.CCitation, 16 U.S.C. §§ 791a–828c]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: U.S.CCitation Context triple: [Federal Power Act, U.S.CCitation, 16 U.S.C. §§ 791a–828c]
-
A.
constitutionalCitation
Indicates a relationship where one entity cites, references, or is grounded in a specific provision or article of a constitution.
-
B.
uscCitation
chosen
Indicates that one legal authority cites or references a provision of the United States Code (U.S.C.).
-
C.
titleOfU.S.Code
Indicates that a specified title number or name corresponds to a particular section or portion of the United States Code.
-
D.
legalCitation
Indicates that one legal document, case, or authority formally references or cites another as a source of legal support or precedent.
-
E.
statutesAtLargeCitation
Indicates that one entity cites or is referenced by a specific citation in the United States Statutes at Large.
- 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_69a8862f7074819096afe7fe65e179e9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb0f79fbc819085c54f3189a552d9 |
completed | March 7, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69abafe2b56c81909e13d543982e6e13 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.