Triple
T12246204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Restatement (Second) of Contracts |
E291858
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | secondary authority in U.S. law |
C31156
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: secondary authority in U.S. law Context triple: [Restatement (Second) of Contracts, instanceOf, secondary authority in U.S. law]
-
A.
United States state law
United States state law is the body of legal rules, regulations, and judicial decisions enacted and applied by an individual U.S. state to govern conduct, resolve disputes, and organize governmental powers within its jurisdiction.
-
B.
combined authority
A combined authority is a legal entity formed by two or more local government areas that collaborate to exercise shared strategic powers and responsibilities, typically over transport, economic development, and regional planning.
-
C.
secondary rules of state responsibility
Secondary rules of state responsibility are the legal principles that determine when and how a state is held internationally responsible for wrongful acts, including attribution, breach, excuses, and the forms and consequences of reparation.
-
D.
supreme law
The supreme law is the highest legal authority in a jurisdiction, such as a constitution, to which all other laws and government actions must conform.
-
E.
United States federal law
United States federal law is the body of statutes, regulations, and legal principles enacted or authorized by the federal government that governs nationwide matters under the U.S. Constitution.
- F. None of above. chosen
Provenance (1 batch)
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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:51 p.m.