Triple
T1237501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sixtus V |
E26580
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 16th-century religious leader |
C605
|
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: 16th-century religious leader Context triple: [Sixtus V, instanceOf, 16th-century religious leader]
-
A.
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.
-
B.
16th-century writer
A 16th-century writer is an author who produced literary, scholarly, or polemical works during the 1500s, often reflecting the cultural, religious, and political transformations of the Renaissance and Reformation eras.
-
C.
Scottish Reformer
A Scottish Reformer is a historical or contemporary figure from Scotland who actively advocates for significant religious, political, or social change, often challenging established institutions to promote reform.
-
D.
religious figure
chosen
A religious figure is an individual recognized within a faith tradition as a spiritual leader, teacher, or exemplar who guides, influences, or embodies the beliefs and practices of that religion.
-
E.
16th-century theological document
A 16th-century theological document is a written work from the 1500s that articulates, debates, or codifies religious doctrines, beliefs, or practices within the historical context of Reformation-era Christianity.
- 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_69a4948571c88190a9191e451e6035fd |
completed | March 1, 2026, 7:33 p.m. |
Created at: March 1, 2026, 7:47 p.m.