Triple
T23377242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy League (France) |
E593640
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | religious-political alliance |
C10026
|
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-political alliance Context triple: [Holy League (France), instanceOf, religious-political alliance]
-
A.
religious and political alliance
chosen
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.
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.
political alliance in Israel
A political alliance in Israel is a temporary or long-term coalition of two or more political parties that join forces to contest elections, coordinate policy positions, and increase their collective influence in the Knesset and government formation.
-
D.
political union
A political union is a formal association of two or more political entities that share or merge governance structures to coordinate policies, laws, and collective decision-making.
-
E.
Indian political alliance
An Indian political alliance is a coalition of two or more political parties in India that collaborate to contest elections, share resources, and pursue common policy goals while retaining their individual identities.
- 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_69e25d268a50819095f2fd479da8ef3f |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:33 p.m.