Triple
T34685141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drei Bünde im Veltlin und Chiavenna |
E890722
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical political association |
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 political association Context triple: [Drei Bünde im Veltlin und Chiavenna, instanceOf, historical political association]
-
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 organization
A political organization is a structured group of individuals who collectively pursue specific political goals, such as influencing public policy, gaining or maintaining power, or representing particular interests within a political system.
-
C.
historical group
A historical group is a collection of people connected by a shared identity, purpose, or activity that existed and acted within a specific past time period.
-
D.
historical political system
A historical political system is an organized structure of governance, power relations, and institutions that operated within a specific society and time period, shaping how authority was distributed, exercised, and justified.
-
E.
religious and political alliance
A religious and political alliance is a coalition in which faith-based groups and political actors formally or informally coordinate their agendas, resources, and influence to pursue shared ideological, social, or policy goals.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:05 a.m.