Triple
T37737287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malla republics |
E940309
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient republics |
C65881
|
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: ancient republics Context triple: [Malla republics, instanceOf, ancient republics]
-
A.
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.
-
B.
historical polities
Historical polities are organized political entities or governing structures that existed in the past, such as kingdoms, empires, city-states, and federations, defined by their territorial control, institutions, and sociopolitical systems.
-
C.
client state of the Roman Republic
A client state of the Roman Republic was a formally independent polity that, through treaties or coercion, accepted Roman supremacy in foreign policy, military support, and often internal affairs in exchange for protection and limited autonomy.
-
D.
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.
-
E.
Etruscan political organization
Etruscan political organization consisted of independent city-states governed by powerful aristocratic elites and priest-kings, loosely united in a religious and political league that coordinated common interests without forming a centralized state.
- 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_69f76edefd048190a32212c5c3919531 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.