Triple
T9962788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papyrus 66 |
E195608
|
entity |
| Predicate | approximateLinesPerPage |
P85106
|
FINISHED |
| Object | about 15–25 lines per page |
—
|
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: about 15–25 lines per page | Statement: [Papyrus 66, approximateLinesPerPage, about 15–25 lines per page]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateLinesPerPage Context triple: [Papyrus 66, approximateLinesPerPage, about 15–25 lines per page]
-
A.
linesPerPage
chosen
Indicates the number of lines that are contained or displayed on a single page.
-
B.
hasPageCountApprox
Indicates that an entity is associated with an approximate or estimated number of pages, rather than an exact page count.
-
C.
sectionCountApproximate
Indicates that the number of sections associated with an entity is known only approximately rather than as an exact count.
-
D.
hasApproximateLineCount
Indicates that one entity is associated with an estimated or non-exact number of lines represented by the other entity.
-
E.
pageSize
Indicates the size or amount of content (such as items, records, or data) that is included or displayed on a single page.
- 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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb718cd588190a4aac48220deddec |
completed | April 2, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:47 p.m.