Triple
T4484050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantis Appendix |
E107192
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 17th-century map publication |
C1302
|
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 map publication Context triple: [Atlantis Appendix, instanceOf, 17th-century map publication]
-
A.
17th-century book
chosen
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.
-
B.
eighteenth-century publication
An eighteenth-century publication is a printed work—such as a book, pamphlet, periodical, or broadside—produced and distributed between 1700 and 1799, reflecting the printing technologies, literary forms, and cultural contexts of that era.
-
C.
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.
-
D.
Renaissance treatise
A Renaissance treatise is a systematic, often humanist-influenced written work from roughly the 14th to 17th centuries that explores a specific subject—such as art, science, politics, or philosophy—through structured argument and scholarly discourse.
-
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_69bd43f84f788190a1383579c4a595be |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 12:58 p.m.