Triple
T19074913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codex Leningradensis |
E466878
|
entity |
| Predicate | scriptoriumType |
P134225
|
FINISHED |
| Object | Jewish scriptorium |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Jewish scriptorium | Statement: [Codex Leningradensis, scriptoriumType, Jewish scriptorium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptoriumType Context triple: [Codex Leningradensis, scriptoriumType, Jewish scriptorium]
-
A.
scriptorium
Indicates that an entity is a place or facility where texts are written, copied, or produced, typically by scribes.
-
B.
scriptoriumStatus
Indicates the current operational or functional state of a scriptorium within a given context.
-
C.
inscriptionType
Indicates the specific kind or category of inscription associated with an entity (e.g., dedicatory, funerary, commemorative).
-
D.
spireType
Indicates the specific architectural or structural style or category that a spire belongs to.
-
E.
epigraphicType
Indicates the specific kind or category of an inscription as classified in epigraphic studies.
- F. None of above. chosen
Provenance (4 batches)
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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e3c7b08190bf6448ead11ba916 |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.