Triple
T20514290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liga |
E503643
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | religious alliance |
C10271
|
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: religious alliance Context triple: [Liga, instanceOf, religious alliance]
-
A.
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.
-
B.
religious league
chosen
A religious league is an organized alliance of states, groups, or individuals united primarily by shared religious beliefs or interests to pursue common political, military, or social goals.
-
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.
religious umbrella organization
A religious umbrella organization is a coordinating body that unites and represents multiple related religious groups, denominations, or institutions under a common framework for shared governance, advocacy, and collaboration.
-
E.
Protestant federation
A Protestant federation is an organized alliance of Protestant churches or denominations that collaborate to coordinate religious activities, represent shared interests, and promote common theological or social goals while maintaining their individual autonomy.
- 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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:36 a.m.