Triple
T36007210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freycinet Plan |
E1041304
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | French government policy |
C31667
|
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 government policy Context triple: [Freycinet Plan, instanceOf, French government policy]
-
A.
French government program
chosen
A French government program is an organized set of public policies, measures, and resources implemented by the French state to achieve specific social, economic, cultural, or environmental objectives.
-
B.
government of France
The government of France is the political and administrative system through which the French Republic is governed, comprising the executive, legislative, and judicial branches that create, implement, and interpret laws and policies.
-
C.
French government cabinet
The French government cabinet is the collective body of ministers, led by the Prime Minister, responsible for directing national policy and administering the executive functions of the French state under the authority of the President.
-
D.
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.
-
E.
French military government
A French military government is a form of administration in which the French armed forces exercise governing authority over a territory, typically during or after military operations, in place of civilian rule.
- 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_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.