Triple
T14023905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Complutensian Polyglot Bible |
E337405
|
entity |
| Predicate | printingCompleted |
P112519
|
FINISHED |
| Object | 1517 |
—
|
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: 1517 | Statement: [Complutensian Polyglot Bible, printingCompleted, 1517]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: printingCompleted Context triple: [Complutensian Polyglot Bible, printingCompleted, 1517]
-
A.
printedFor
Indicates that one entity produced a printed version of something specifically intended for another entity as the recipient or audience.
-
B.
printedBy
Indicates that one entity is produced or output in physical or digital form by another entity acting as the printer or printing agent.
-
C.
printedOn
Indicates that something is produced or reproduced in physical form on a specified material, surface, or medium.
-
D.
printingCenter
Indicates a relationship where one entity serves as the printing center (i.e., the facility or service that performs printing) for another entity.
-
E.
printedInColor
Indicates that something was produced or reproduced using multiple ink colors rather than only black-and-white.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f3d87b88190b038d334f4965369 |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239524688190a0f2408c239cfcaa |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:19 p.m.