Triple
T17553482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King’s Printer to Edward VI |
E427529
|
entity |
| Predicate | authorizedToPrint |
P18111
|
FINISHED |
| Object | English Bibles |
—
|
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: English Bibles | Statement: [King’s Printer to Edward VI, authorizedToPrint, English Bibles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorizedToPrint Context triple: [King’s Printer to Edward VI, authorizedToPrint, English Bibles]
-
A.
printingAuthority
chosen
Indicates the entity responsible for producing or issuing a physical or printed version of another entity.
-
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.
printedFor
Indicates that one entity produced a printed version of something specifically intended for another entity as the recipient or audience.
-
D.
isPrinted
Indicates that a physical copy of an item has been produced using a printing process.
-
E.
printedOn
Indicates that something is produced or reproduced in physical form on a specified material, surface, or medium.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4561fcaf48190b2e45b77e5ff7d0f |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.