Triple
T29431222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic of Ancona |
E746437
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval maritime republic |
C7983
|
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 republic Context triple: [Republic of Ancona, instanceOf, medieval maritime republic]
-
A.
maritime republic
chosen
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.
-
B.
institution of the Republic of Venice
An institution of the Republic of Venice is an organized political, legal, religious, or economic body established by the Venetian state to govern, administer, or regulate aspects of public life within its maritime and territorial domains.
-
C.
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.
-
D.
group of medieval polities
A group of medieval polities is a collection of semi-autonomous kingdoms, principalities, city-states, or other territorial entities that interacted through shifting alliances, conflicts, and hierarchies within the broader sociopolitical landscape of the Middle Ages.
-
E.
maritime confederation
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.
- 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 3:13 p.m.