Triple
T5076715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carl Gustav Rehnskiöld |
E114414
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military commander in the Great Northern War |
C17497
|
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: military commander in the Great Northern War Context triple: [Carl Gustav Rehnskiöld, instanceOf, military commander in the Great Northern War]
-
A.
Polish military leader
A Polish military leader is a high-ranking commander from Poland responsible for planning, directing, and overseeing military operations and the strategic use of armed forces in defense of the nation.
-
B.
military commander in New France
A military commander in New France was a royal appointee responsible for organizing, leading, and coordinating French colonial troops and allied Indigenous forces to defend and expand the colony’s territories in North America.
-
C.
medieval military leader
A medieval military leader is a high-ranking commander responsible for organizing, directing, and inspiring armed forces in warfare during the Middle Ages, often balancing battlefield tactics with feudal, political, and religious obligations.
-
D.
Dutch general
A Dutch general is a high-ranking military officer from the Netherlands responsible for leading and overseeing major army operations, strategy, and personnel.
-
E.
17th-century Swedish monarch
A 17th-century Swedish monarch is a sovereign ruler of Sweden during the 1600s who governed the kingdom’s political, military, and religious affairs amid major European conflicts and internal state-building.
- 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_69bd443dbf908190a9401e9c2dc7bd7d |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:39 p.m.