Triple
T8896229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codex Ephraemi Rescriptus |
E211810
|
entity |
| Predicate | linesPerPage |
P85106
|
FINISHED |
| Object | approximately 40 to 46 |
—
|
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: approximately 40 to 46 | Statement: [Codex Ephraemi Rescriptus, linesPerPage, approximately 40 to 46]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linesPerPage Context triple: [Codex Ephraemi Rescriptus, linesPerPage, approximately 40 to 46]
-
A.
pageSize
Indicates the size or amount of content (such as items, records, or data) that is included or displayed on a single page.
-
B.
pages
Indicates that one entity consists of or contains a certain number of pages, or that a specific page-related attribute is associated with it.
-
C.
codePageNumber
Indicates the specific page number within a code document or code listing where something is located or referenced.
-
D.
leafletsPerLeaf
Indicates the number of individual leaflets that are present on each single leaf.
-
E.
hasPageCountApprox
Indicates that an entity is associated with an approximate or estimated number of pages, rather than an exact page count.
- 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_69ca83918d3081909b326fa3750cb8c8 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc61bfec0881908e4ef5b7f0e6b542 |
completed | April 1, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2bfb38819083d5eb1af8ccf4d6 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cffe8ec819084c12770fe0578f2 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:54 p.m.