Triple
T25849313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy League against the Turks |
E651156
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 16th-century alliance |
C10272
|
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: 16th-century alliance Context triple: [Holy League against the Turks, instanceOf, 16th-century alliance]
-
A.
early modern political alliance
chosen
An early modern political alliance is a formal or informal agreement between states, dynasties, or political entities from roughly the 15th to 18th centuries to cooperate for mutual security, territorial, economic, or dynastic advantage within a shifting balance-of-power system.
-
B.
16th-century conflict
A 16th-century conflict is a historically documented military, political, or religious struggle that occurred between 1501 and 1600, involving organized groups or states and significantly influencing the social and geopolitical landscape of the early modern period.
-
C.
historical alliance
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.
-
D.
16th-century council
A 16th-century council is a formal assembly of political, religious, or civic authorities convened during the 1500s to deliberate and decide on matters of governance, doctrine, law, or public policy.
-
E.
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.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 7:58 a.m.