Triple
T35889974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venetian rectors |
E1037753
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Venetian colonial officials |
C63132
|
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: Venetian colonial officials Context triple: [Venetian rectors, instanceOf, Venetian colonial officials]
-
A.
Spanish colonial governor
A Spanish colonial governor was the crown-appointed official responsible for administering, defending, and representing royal authority in a designated overseas territory of the Spanish Empire.
-
B.
Ottoman provincial governors
Ottoman provincial governors were imperial officials appointed by the sultan to administer provinces, collect taxes, maintain order, and implement central policies while balancing local power structures within the Ottoman Empire.
-
C.
Venetian family
A Venetian family is a social unit rooted in Venice’s unique historical, cultural, and economic context, typically characterized by strong kinship ties, intergenerational traditions, and connections to the city’s maritime, mercantile, or artistic heritage.
-
D.
Venetian senator
A Venetian senator was a high-ranking member of the governing council of the Republic of Venice, responsible for advising the Doge and shaping the city-state’s foreign and domestic policy.
-
E.
Genoese colony
A Genoese colony was a territorial possession or trading outpost established and administered by the Republic of Genoa to control maritime commerce, strategic ports, and regional influence across the Mediterranean and Black Sea.
- 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.