Triple
T9276305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanseatic Diet |
E222956
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | institution of the Hanseatic League |
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: institution of the Hanseatic League Context triple: [Hanseatic Diet, instanceOf, institution of the Hanseatic League]
-
A.
historic confederation of towns
A historic confederation of towns is a formal alliance of multiple municipalities that cooperatively coordinate defense, trade, governance, or mutual support while retaining their individual local autonomy.
-
B.
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.
-
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.
assembly of the Holy Roman Empire
The assembly of the Holy Roman Empire was a representative gathering of the Empire’s princes, ecclesiastical leaders, and imperial cities convened to deliberate and decide on matters of law, policy, and governance under the authority of the emperor.
-
E.
imperial state of the Holy Roman Empire
An imperial state of the Holy Roman Empire was a semi-autonomous political entity—such as a duchy, principality, city, or ecclesiastical territory—directly subject to the authority of the emperor and the imperial diet rather than to any intermediate lord.
- 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_69ca841ffe208190aa7bcffbef2f8379 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:34 p.m.