Triple
T36217235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Directoire français |
E1047732
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | période historique française |
C138
|
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: période historique française Context triple: [Directoire français, instanceOf, période historique française]
-
A.
history of the French Revolution
The history of the French Revolution examines the political, social, economic, and cultural causes, events, and consequences of the upheaval in France from 1789 to 1799 that transformed the nation and influenced modern democratic and revolutionary movements worldwide.
-
B.
historical period
chosen
A historical period is a span of time characterized by distinct social, political, cultural, or technological conditions that differentiate it from other eras in history.
-
C.
aspect of French history
An aspect of French history is a distinct theme, period, event, or social, political, or cultural development that significantly shaped the evolution of France and its identity over time.
-
D.
Frankish historiography
Frankish historiography is the body of historical writing produced in or about the Frankish realms, encompassing chronicles, annals, saints’ lives, and other narratives that construct and interpret the political, religious, and cultural history of the Franks from late antiquity through the early Middle Ages.
-
E.
historical topic
A historical topic is a specific subject, event, period, or theme from the past that is studied, analyzed, and interpreted to understand historical developments and their impact.
- 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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.