Triple
T10675848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacob Brown |
E251613
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | War of 1812 commander |
C18479
|
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: War of 1812 commander Context triple: [Jacob Brown, instanceOf, War of 1812 commander]
-
A.
War of 1812 participant
chosen
A War of 1812 participant is an individual, military unit, or entity that took part in the military, political, or support activities associated with the War of 1812 between the United States, the British Empire, and their respective allies.
-
B.
military commander in the Great Northern War
A military commander in the Great Northern War is a high-ranking officer responsible for planning and directing land or naval operations among the warring Northern and Eastern European powers between 1700 and 1721.
-
C.
Military leader
A military leader is an individual who plans, directs, and coordinates armed forces operations, making strategic and tactical decisions to achieve military objectives while managing and motivating personnel under their command.
-
D.
Commander-in-chief
The Commander-in-chief is the highest-ranking authority responsible for the overall command, strategic direction, and ultimate decision-making of a nation's armed forces.
-
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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:09 p.m.