Triple
T34852675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | medieval Vicenza |
E1004641
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Italian city |
C9063
|
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 Italian city Context triple: [medieval Vicenza, instanceOf, medieval Italian city]
-
A.
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.
-
B.
medieval city
chosen
A medieval city is a densely populated, fortified urban center characterized by narrow winding streets, defensive walls, a central marketplace, religious and administrative buildings, and distinct social and economic quarters.
-
C.
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.
-
D.
metropolitan city of Italy
A metropolitan city of Italy is a large urban area and its surrounding municipalities governed as a single administrative entity with special powers for planning, infrastructure, and local services.
-
E.
Renaissance town
A Renaissance town is an urban settlement characterized by humanist-inspired planning, harmonious proportions, and architecture that blends classical forms with emerging civic, commercial, and cultural functions of the 14th–17th centuries.
- 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.