Triple
T3026138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayard (Pierre Terrail, seigneur de Bayard) |
E82578
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Italian Wars military personnel |
C13086
|
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: Italian Wars military personnel Context triple: [Bayard (Pierre Terrail, seigneur de Bayard), instanceOf, Italian Wars military personnel]
-
A.
European war
A European war is a large-scale armed conflict primarily involving multiple nation-states within Europe, often driven by territorial, political, or ideological disputes that significantly reshape the continent’s balance of power.
-
B.
military personnel of the French Revolutionary Wars
Individuals who served in the armed forces of France or opposing states during the French Revolutionary Wars (1792–1802), participating in military operations, command, support, or related roles.
-
C.
imperial war
Imperial war is a large-scale, often expansionist conflict waged by an empire to acquire, control, or maintain dominance over territories, peoples, or resources beyond its original borders.
-
D.
historical armed forces
Historical armed forces are organized military institutions from past eras, composed of soldiers, equipment, and command structures, created by states or societies to conduct warfare, defend territories, and project power.
-
E.
participants in military alliance
Participants in a military alliance are sovereign states or entities that formally agree to cooperate in defense and security matters, sharing obligations, resources, and strategic commitments against common threats.
- F. None of above. chosen
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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3 p.m.