Triple
T32021239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick Roberts, 1st Earl Roberts |
E817695
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Victorian era military commander |
C16128
|
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: Victorian era military commander Context triple: [Frederick Roberts, 1st Earl Roberts, instanceOf, Victorian era military commander]
-
A.
Georgian military commander
A Georgian military commander is a high-ranking officer from Georgia responsible for planning, directing, and overseeing military operations and strategy within the Georgian armed forces.
-
B.
Saxon field marshal
A Saxon field marshal is a highest-ranking military officer from Saxony responsible for commanding large armies, directing overall strategy, and overseeing major military operations.
-
C.
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.
-
D.
19th-century military leader
chosen
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.
-
E.
Welsh military officer
A Welsh military officer is a commissioned or non-commissioned member of the armed forces from Wales, responsible for leading, training, and managing soldiers while planning and executing military operations.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:16 a.m.