Triple
T16816685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jakub Jasiński |
E408769
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish–Lithuanian Commonwealth military personnel |
C37879
|
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: Polish–Lithuanian Commonwealth military personnel Context triple: [Jakub Jasiński, instanceOf, Polish–Lithuanian Commonwealth military personnel]
-
A.
Polish military position
A Polish military position is an organized role or rank within Poland's armed forces, defined by specific duties, authority, and responsibilities in the national defense structure.
-
B.
Polish military institution
A Polish military institution is an organization established by the Polish state to manage, train, support, or command elements of the armed forces in accordance with national defense policies and legal frameworks.
-
C.
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.
-
D.
Polish military history event
A Polish military history event is a significant occurrence involving Poland’s armed forces—such as battles, campaigns, uprisings, operations, or strategic decisions—that influenced the course of Poland’s national or military development.
-
E.
Slovak military officer
A Slovak military officer is a commissioned member of Slovakia’s armed forces responsible for leading personnel, planning and executing military operations, and upholding national defense and security policies.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
Created at: April 10, 2026, 5:23 a.m.