Triple
T15869822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venetian Senate |
E384803
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | institution of the Republic of Venice |
C36584
|
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 Republic of Venice Context triple: [Venetian Senate, instanceOf, institution of the Republic of Venice]
-
A.
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.
-
B.
organ of the Republic of Genoa
An organ of the Republic of Genoa is an official governing body or institutional component responsible for exercising specific political, administrative, judicial, or financial functions within the Genoese state.
-
C.
Lombard principality
A Lombard principality is a semi-autonomous medieval political entity ruled by Lombard nobility, typically emerging from the fragmentation of the Lombard Kingdom in Italy and characterized by its own local governance, military, and legal traditions.
-
D.
Italian city-state
An Italian city-state is an independent, self-governing urban center and its surrounding territory on the Italian peninsula, typically flourishing in the medieval and Renaissance periods through commerce, politics, and culture.
-
E.
Florentine magistracy
The Florentine magistracy was the complex system of elected and rotating civic offices that governed the Republic of Florence, balancing power among guilds, factions, and social groups through short terms and collective decision-making.
- F. None of above. chosen
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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:50 a.m.