Triple
T28492710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lithuanian–Polish forces |
E721019
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical military alliance |
C24628
|
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: historical military alliance Context triple: [Lithuanian–Polish forces, instanceOf, historical military alliance]
-
A.
historical alliance
chosen
A historical alliance is a formal or informal partnership between states, groups, or leaders formed in the past to pursue shared political, military, economic, or cultural goals.
-
B.
political-military alliance
A political-military alliance is a formal agreement between two or more states to coordinate their defense and foreign policies, often including mutual security guarantees and joint military planning.
-
C.
Catholic military alliance
A Catholic military alliance is a coalition of armed forces from predominantly Catholic states or groups, formed to defend shared religious, political, or territorial interests under a common Catholic identity.
-
D.
treaty-based alliance
A treaty-based alliance is a formal agreement between two or more sovereign entities that legally binds them to cooperate on specified political, military, economic, or other mutual interests under defined terms and obligations.
-
E.
military alliance pattern
A military alliance pattern is a recurring strategic arrangement in which multiple states or actors coordinate defense commitments, resource sharing, and joint planning to deter threats and enhance collective security.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:02 a.m.