Triple
T3124606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Foley |
E65266
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British military personnel of the Napoleonic Wars |
C12267
|
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: British military personnel of the Napoleonic Wars Context triple: [Thomas Foley, instanceOf, British military personnel of the Napoleonic Wars]
-
A.
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.
-
B.
French Revolutionary army
The French Revolutionary army was the mass conscripted military force of revolutionary France that combined ideological zeal, innovative organization, and large citizen armies to defend and spread the Revolution across Europe.
-
C.
British military personnel killed in World War II
Individuals who served in the British armed forces and lost their lives as a direct result of military service during World War II.
-
D.
British Army organizational element
A British Army organizational element is a defined structural unit—such as a section, platoon, company, battalion, brigade, or division—comprising personnel, equipment, and command relationships arranged to perform specific military roles within the Army’s hierarchy.
-
E.
British Army deployment
British Army deployment is the organized assignment and movement of British Army personnel and resources to specific locations or operations to fulfill military objectives and commitments.
- 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_69ad8580c72481909672d37acf647893 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:04 p.m.