Triple
T15232837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pskov Republic |
E364047
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval republic |
C4114
|
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 republic Context triple: [Pskov Republic, instanceOf, medieval republic]
-
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.
medieval polity
chosen
A medieval polity is a territorially based political entity of the Middle Ages—such as a kingdom, duchy, city-state, or principality—defined by overlapping authorities, personal allegiances, and often fragmented sovereignty rather than a centralized nation-state structure.
-
C.
ancient republic
An ancient republic is a form of government in classical antiquity where political power is held by a body of citizens and their elected or appointed representatives, rather than by a monarch.
-
D.
medieval city
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.
-
E.
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.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:12 a.m.