Triple
T4077943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codex Mendoza |
E87408
|
entity |
| Predicate | approximatePages |
P9415
|
FINISHED |
| Object | 71 folios |
—
|
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: 71 folios | Statement: [Codex Mendoza, approximatePages, 71 folios]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximatePages Context triple: [Codex Mendoza, approximatePages, 71 folios]
-
A.
hasPageCountApprox
chosen
Indicates that an entity is associated with an approximate or estimated number of pages, rather than an exact page count.
-
B.
approximateNumberOfVerses
Indicates an estimated or approximate count of verses associated with an entity.
-
C.
approximateSize
Indicates that one entity has a size that is roughly or approximately equal to the size of another entity.
-
D.
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.
-
E.
approximates
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc4d348c8190a94724639830aca0 |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9082c2081908474f082a49bebc8 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.