Triple
T12487838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epinay Congress |
E298482
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | French political event |
C238
|
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 political event Context triple: [Epinay Congress, instanceOf, French political event]
-
A.
French political organisation
A French political organisation is a structured group operating within France’s political system to influence public policy, represent interests, or compete for governmental power in accordance with French law and institutions.
-
B.
event of the French Revolution
An event of the French Revolution is a historically specific occurrence between 1789 and 1799 in France that significantly influenced the revolution’s political, social, or cultural trajectory.
-
C.
episode of the French Revolution
An episode of the French Revolution is a distinct historical event or sequence of actions occurring within the broader revolutionary period, involving specific actors, locations, and political or social developments.
-
D.
political event
chosen
A political event is a planned or spontaneous occurrence involving political actors, institutions, or the public that aims to influence, express, or respond to political power, policy, or public opinion.
-
E.
political office in France
A political office in France is an official position within the French governmental or administrative system, held by an elected or appointed individual responsible for exercising public authority and implementing state or local policies.
- 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_69d6ada377208190a36011199a4d8558 |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:56 p.m.