Triple
T34390929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rossano |
E882699
|
entity |
| Predicate | codexContent |
P16933
|
FINISHED |
| Object | illuminated Gospel manuscript (Codex Purpureus Rossanensis) |
—
|
NE NERFINISHED |
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: illuminated Gospel manuscript (Codex Purpureus Rossanensis) | Statement: [Rossano, codexContent, illuminated Gospel manuscript (Codex Purpureus Rossanensis)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codexContent Context triple: [Rossano, codexContent, illuminated Gospel manuscript (Codex Purpureus Rossanensis)]
-
A.
codicesFunctionAs
Indicates that certain codices serve a particular role, purpose, or function in relation to something else.
-
B.
book5Content
chosen
Indicates that one entity is the content or textual material contained within the book represented by the other entity.
-
C.
foundInCodexWith
Indicates that one entity is documented together with another entity within the same codex or manuscript.
-
D.
scholarlyApparatus
Indicates the relationship in which a work provides critical tools—such as notes, commentary, or references—that support, explain, or contextualize another text or body of material.
-
E.
sisterCodex
Indicates a sibling relationship where one codex or text is considered a sister counterpart to another, typically implying close similarity, shared origin, or parallel status.
- F. None of above.
Provenance (3 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_69f349c0219881909393bbbc1edc8161 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 1:59 a.m.