Triple
T3735592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard William Howard Vyse |
E79174
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British army officer |
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 army officer Context triple: [Richard William Howard Vyse, instanceOf, British army officer]
-
A.
British military leader
A British military leader is a high-ranking officer from the United Kingdom responsible for planning, directing, and overseeing military operations and strategy, often commanding troops in national defense or international conflicts.
-
B.
British Army veteran
A British Army veteran is a former member of the United Kingdom's land warfare force who has completed their service, whether in peacetime or conflict, and is recognized for their military contribution.
-
C.
British civil servant
A British civil servant is a non-political government employee who supports the administration and implementation of public policy within the United Kingdom’s civil service.
-
D.
British military personnel of the Napoleonic Wars
chosen
Individuals who served in the armed forces of the United Kingdom during the Napoleonic Wars (circa 1803–1815), including soldiers, sailors, and officers involved in military operations against Napoleonic France and its allies.
-
E.
British colonial administrator
A British colonial administrator is an official appointed by the British government to govern, manage, and implement imperial policies in overseas colonies, overseeing local administration, law, and economic exploitation.
- 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:34 p.m.