Triple
T6552634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law of Obligations |
E151165
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of civil law |
C21569
|
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: branch of civil law Context triple: [Law of Obligations, instanceOf, branch of civil law]
-
A.
civil law tradition
The civil law tradition is a legal system rooted in comprehensive written codes and statutes, derived primarily from Roman law, in which judges apply and interpret codified rules rather than relying heavily on judicial precedent.
-
B.
branch of administrative law
A branch of administrative law is a specialized area within the broader field that governs the organization, powers, procedures, and accountability of public administrative agencies in a particular domain (such as environmental regulation, immigration, or social welfare).
-
C.
source of civil procedural law
A source of civil procedural law is any formally recognized authority—such as constitutions, statutes, court rules, judicial precedents, and international treaties—that establishes or influences the rules governing the conduct of civil litigation.
-
D.
codification of private law
Codification of private law is the systematic collection and organization of rules governing relationships between private individuals and entities into a coherent, comprehensive legal code.
-
E.
system of laws
A system of laws is an organized and coherent set of rules and principles established by an authority to regulate behavior, resolve disputes, and maintain order within a society.
- 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_69c687f3fd60819083bfa583e5bcfa71 |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 1:51 p.m.