Triple
T24075455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Code pénal |
E596347
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | French criminal code |
C7807
|
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: French criminal code Context triple: [Code pénal, instanceOf, French criminal code]
-
A.
French statute
chosen
A French statute is a formal written law enacted by the French Parliament or, in certain cases, by referendum, that establishes general and permanent legal rules applicable within the French legal system.
-
B.
French department code
A French department code is a standardized numerical or alphanumerical identifier assigned to each administrative department in France for use in postal addresses, vehicle registration, statistics, and various official records.
-
C.
Prussian law
Prussian law refers to the body of legal principles, statutes, and judicial practices that governed the Kingdom of Prussia, characterized by a strong centralized authority, codification efforts like the Allgemeines Landrecht, and an emphasis on bureaucratic administration and social order.
-
D.
Belgian federal law
Belgian federal law is the body of legal rules and principles enacted or recognized by the federal institutions of Belgium that apply uniformly across the entire country on matters within federal competence, such as justice, defense, social security, and monetary policy.
-
E.
barbarian law code
A barbarian law code is a written compilation of legal customs and rules created by early medieval Germanic or other so‑called “barbarian” peoples, often blending tribal traditions with Roman legal influences.
- 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_69e288c3999c8190809b282a04813dec |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 10:42 p.m.