Triple
T11943699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitma resettlement system |
E284241
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Inca imperial policy |
C30654
|
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: Inca imperial policy Context triple: [Mitma resettlement system, instanceOf, Inca imperial policy]
-
A.
Inca polity
The Inca polity was a highly centralized, hierarchical imperial state in the Andes that integrated diverse ethnic groups through a complex system of administration, tribute, and state-sponsored religion centered on the Sapa Inca.
-
B.
battle of the Spanish conquest of Peru
A battle of the Spanish conquest of Peru is a specific military engagement between Spanish conquistadors and Indigenous forces that occurred during the 16th-century campaign to subjugate and colonize the Inca Empire.
-
C.
Roman imperial policy
Roman imperial policy refers to the strategies, laws, and administrative practices employed by Roman emperors to maintain control, integrate diverse provinces, manage resources, and project power across the empire.
-
D.
Inca road system
The Inca road system was an extensive, sophisticated network of paved and unpaved routes spanning thousands of kilometers across the Andes, designed to connect and administer the vast Inca Empire through efficient communication, trade, and military movement.
-
E.
Inca emperor
The Inca emperor was the supreme political, religious, and military ruler of the Inca Empire, regarded as a divine descendant of the sun god Inti who governed from the capital of Cusco.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:45 p.m.