Triple
T14805770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | government of Carthage |
E348030
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient political system |
C22070
|
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 political system Context triple: [government of Carthage, instanceOf, ancient political system]
-
A.
historical political system
chosen
A historical political system is an organized structure of governance, power relations, and institutions that operated within a specific society and time period, shaping how authority was distributed, exercised, and justified.
-
B.
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.
-
C.
colonial political organization
A colonial political organization is a governing structure imposed by a foreign power to administer, control, and exploit a colonized territory and its population, often subordinating local institutions and interests to imperial objectives.
-
D.
agrarian political organization
An agrarian political organization is a group that advocates for the interests, rights, and policy priorities of rural communities and agricultural producers within a political system.
-
E.
agrarian political organization
An agrarian political organization is a group that mobilizes and represents the interests of rural communities and agricultural producers to influence public policy, land use, and economic conditions affecting farming and countryside livelihoods.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:34 a.m.