Triple
T15244947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinakes |
E364354
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient bibliographic catalog |
C34400
|
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: ancient bibliographic catalog Context triple: [Pinakes, instanceOf, ancient bibliographic catalog]
-
A.
ancient library
An ancient library is a vast, timeworn repository of knowledge, filled with fragile scrolls, faded manuscripts, and stone-carved records that preserve the wisdom, myths, and histories of long-lost civilizations.
-
B.
manuscript catalogue
chosen
A manuscript catalogue is a systematically organized listing that describes and indexes individual manuscripts within a collection, typically including details such as authorship, date, provenance, physical characteristics, and content summaries.
-
C.
ancient manuscripts
Ancient manuscripts are original handwritten documents from past civilizations, typically preserved on materials like papyrus, parchment, or early paper, that provide primary evidence of historical, religious, literary, or scientific thought.
-
D.
library cataloging tool
A library cataloging tool is a system that helps librarians and users organize, classify, and retrieve library materials efficiently through standardized metadata and search functions.
-
E.
cataloging record
A cataloging record is a structured set of metadata describing a resource (such as a book, media item, or digital object) to enable its identification, organization, and retrieval within a catalog or information system.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:13 a.m.