Triple
T8400867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act on General Rules for Application of Laws |
E198166
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | conflict of laws statute |
C251
|
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: conflict of laws statute Context triple: [Act on General Rules for Application of Laws, instanceOf, conflict of laws statute]
-
A.
statute
chosen
A statute is a formal written law enacted by a legislative body that establishes rules, obligations, or prohibitions within a governing jurisdiction.
-
B.
legal jurisdiction
A legal jurisdiction is a defined geographic area or subject-matter domain within which a particular court or governmental authority has the power to create, interpret, and enforce laws.
-
C.
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.
-
D.
constitutional statute
A constitutional statute is a fundamental law enacted by a legislature that, while formally an ordinary statute, has quasi-constitutional status because it implements, structures, or protects core constitutional principles and cannot be amended or repealed without special procedures or heightened scrutiny.
-
E.
internal statute
An internal statute is a formal, binding rule or regulation adopted within an organization to govern its internal operations, decision-making processes, and member conduct.
- F. None of above.
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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 6:04 p.m.