Triple
T25175573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codex Telleriano-Remensis |
E630437
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 16th-century document |
C36483
|
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 document Context triple: [Codex Telleriano-Remensis, instanceOf, 16th-century document]
-
A.
15th-century document
A 15th-century document is a written or printed record created between 1401 and 1500, reflecting the political, religious, economic, or cultural contexts of late medieval and early Renaissance societies.
-
B.
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.
-
C.
17th-century book
A 17th-century book is a bound collection of printed or handwritten pages produced between 1601 and 1700, reflecting the period’s materials, typography, and intellectual, religious, or political culture.
-
D.
early 16th-century map
chosen
An early 16th-century map is a hand-drawn cartographic representation from the early 1500s that reflects contemporary geographic knowledge, exploration routes, and often decorative or symbolic elements characteristic of Renaissance Europe.
-
E.
16th-century council
A 16th-century council is a formal assembly of political, religious, or civic authorities convened during the 1500s to deliberate and decide on matters of governance, doctrine, law, or public policy.
- 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
Created at: April 21, 2026, 12:34 p.m.