Triple
T9509274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lazare Hoche |
E229349
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | French Revolutionary general |
C18940
|
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 general Context triple: [Lazare Hoche, instanceOf, French Revolutionary general]
-
A.
French military leader
chosen
A French military leader is a high-ranking officer from France responsible for planning, directing, and commanding military operations and forces in defense of national interests.
-
B.
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.
-
C.
Prussian general
A Prussian general is a high-ranking military officer of the historical Kingdom of Prussia, characterized by rigorous discipline, strategic planning, and leadership in organizing and commanding armies in war.
-
D.
Director of the French Directory
The Director of the French Directory was one of five co-equal executive magistrates who collectively governed France between 1795 and 1799, overseeing administration, foreign policy, and the enforcement of laws under the Directory regime.
-
E.
19th-century military leader
A 19th-century military leader is a high-ranking commander who directed armed forces during the 1800s, shaping national and imperial conflicts through strategic planning, battlefield leadership, and political influence.
- 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_69ca847611c48190a28c028644198c75 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 7:58 p.m.