Triple
T3070359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cinque Ports |
E64004
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval maritime alliance |
C3079
|
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: medieval maritime alliance Context triple: [Cinque Ports, instanceOf, medieval maritime alliance]
-
A.
maritime confederation
chosen
A maritime confederation is a loose alliance of seafaring states or cities that cooperate to control trade routes, naval defense, and maritime law while retaining their political independence.
-
B.
maritime kingdom
A maritime kingdom is a sovereign state whose power, economy, and culture are primarily based on seafaring, naval strength, and control of important sea routes and coastal territories.
-
C.
maritime republic
A maritime republic is a city-state or polity whose power, wealth, and political institutions are primarily based on seaborne trade, naval strength, and control of maritime routes.
-
D.
early modern political alliance
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.
-
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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:02 p.m.