Triple
T916959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codex Sinaiticus |
E19792
|
entity |
| Predicate | writingSupport |
P12679
|
FINISHED |
| Object | vellum |
—
|
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: vellum | Statement: [Codex Sinaiticus, writingSupport, vellum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingSupport Context triple: [Codex Sinaiticus, writingSupport, vellum]
-
A.
writingTool
Indicates that one entity serves as a tool or instrument used by another entity for the act of writing.
-
B.
writtenForm
Indicates that one entity is the textual or orthographic representation (spelling or written version) of another entity.
-
C.
writingSystem
Indicates that one entity is the script or system of written symbols used to represent the language or content of another entity.
-
D.
canBeWrittenIn
chosen
Indicates that something is capable of being expressed, encoded, or represented using a particular language, notation, or medium.
-
E.
written
Indicates that one entity has created or authored a text, document, or written work involving or about another entity.
- 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_69a4939f91a08190ba68c2c81eab90fe |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b6755c488190b7f7848110e3ea2c |
completed | March 1, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69a4b292d3408190947cbc2f794cf8c5 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:39 p.m.