Triple
T29952139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Husaria |
E760797
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish–Lithuanian military formation |
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 military formation Context triple: [Husaria, instanceOf, Polish–Lithuanian military formation]
-
A.
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.
-
B.
Polish–Lithuanian Commonwealth military personnel
chosen
Individuals who served in the armed forces of the Polish–Lithuanian Commonwealth, including its army, navy, and related military formations, from its formation in 1569 until its final partitions in the late 18th century.
-
C.
Polish military contingent
A Polish military contingent is a temporary, organized group of Polish Armed Forces personnel and resources deployed for specific missions, operations, or international commitments.
-
D.
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.
-
E.
Habsburg military formation
A Habsburg military formation is an organized unit or arrangement of troops within the armed forces of the Habsburg Monarchy, structured according to its evolving doctrines, hierarchies, and tactical needs from the early modern period through the empire’s dissolution.
- 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:26 p.m.