Triple
T3442513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Funeral Sermon and Prayer |
E72596
|
entity |
| Predicate | manuscriptMedium |
P48838
|
FINISHED |
| Object | parchment |
—
|
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: parchment | Statement: [Funeral Sermon and Prayer, manuscriptMedium, parchment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: manuscriptMedium Context triple: [Funeral Sermon and Prayer, manuscriptMedium, parchment]
-
A.
manuscript
Indicates that an entity is a written or typed document, often a draft or original version of a text, associated with another entity (such as its author, subject, or publication process).
-
B.
manuscriptTradition
Indicates the relationship between a text and the chain of manuscript copying, transmission, and variation through which that text has been preserved and passed down.
-
C.
manuscriptType
Indicates the specific category or kind of manuscript associated with an entity (e.g., draft, final version, annotated copy).
-
D.
manuscriptShelfmark
Indicates the specific shelfmark or call number under which a manuscript is stored or cataloged in a collection.
-
E.
numberOfManuscriptsApprox
Indicates an approximate count of manuscripts associated with an entity.
- 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_69ad85b05c848190b7a28ceec2bd7b74 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adba28ec448190a6a07c5f16235fe3 |
completed | March 8, 2026, 6:04 p.m. |
| PD | Predicate disambiguation | batch_69adae0255b48190a9069f7871c7a012 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb1ecb02881908394f197e31431b4 |
completed | March 8, 2026, 5:29 p.m. |
Created at: March 8, 2026, 3:16 p.m.