Triple
T20692255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amangkurat I |
E508580
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 17th-century monarch |
C43447
|
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: 17th-century monarch Context triple: [Amangkurat I, instanceOf, 17th-century monarch]
-
A.
18th-century ruler
An 18th-century ruler is a sovereign or head of state who governed a territory during the 1700s, navigating the era’s shifting political, economic, and intellectual currents such as absolutism, colonial expansion, and Enlightenment thought.
-
B.
17th-century Swedish monarch
A 17th-century Swedish monarch is a sovereign ruler of Sweden during the 1600s who governed the kingdom’s political, military, and religious affairs amid major European conflicts and internal state-building.
-
C.
16th-century ruler
A 16th-century ruler is a sovereign or monarch who governed a state or territory during the 1500s, navigating the era’s religious upheavals, emerging global trade, and shifting political alliances.
-
D.
14th-century monarch
A 14th-century monarch is a hereditary or elected sovereign who ruled a kingdom or empire during the 1300s, navigating feudal power structures, dynastic politics, warfare, and shifting religious and economic landscapes.
-
E.
13th-century monarch
A 13th-century monarch is a sovereign ruler who governed a kingdom or empire during the 1200s, navigating feudal power structures, dynastic politics, and often religious conflicts to maintain authority and territorial control.
- 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_69e0b4c1ed408190b72dd26b1e33f8a1 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 12:09 p.m.