Triple
T13589119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | maximum on prices |
E324645
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | French Revolutionary law |
C17565
|
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 Revolutionary law Context triple: [maximum on prices, instanceOf, French Revolutionary law]
-
A.
French Revolutionary policy
French Revolutionary policy encompasses the radical political, social, economic, and legal measures enacted between 1789 and 1799 to dismantle the ancien régime, establish popular sovereignty, and reshape French society along Enlightenment and republican principles.
-
B.
revolutionary law
chosen
Revolutionary law is a legal framework or set of principles established during or after a revolution to dismantle the previous regime’s legal order and legitimize the new political and social system.
-
C.
French statute
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.
-
D.
French revolutionary
A French revolutionary is an individual who actively participated in or supported the radical political, social, and cultural transformations during the French Revolution, often advocating for liberty, equality, and the overthrow of the ancien régime.
-
E.
revolutionary court
A revolutionary court is a special judicial body established during periods of political upheaval to rapidly try and punish individuals deemed enemies of the revolution, often with limited legal safeguards.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:49 p.m.