Triple
T30472528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quintuplex Psalterium |
E775342
|
entity |
| Predicate | hasEraOfPrinting |
P77920
|
FINISHED |
| Object | early modern period |
—
|
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: early modern period | Statement: [Quintuplex Psalterium, hasEraOfPrinting, early modern period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEraOfPrinting Context triple: [Quintuplex Psalterium, hasEraOfPrinting, early modern period]
-
A.
hasPublicationEra
Indicates the time period or era during which a publication was released or made publicly available.
-
B.
hasFirstEditionYear
Indicates the year in which the first edition of an item (such as a work, book, or publication) was originally released or published.
-
C.
usedPrintingPressAt
Indicates that one entity operated or made use of a printing press at, or in connection with, another entity (such as a place, time, or event).
-
D.
hasPrimaryEra
chosen
Indicates that an entity is chiefly associated with or belongs to a particular historical or temporal era.
-
E.
approximateDateOfFirstPrinting
Indicates the estimated or uncertain date when an item was first printed.
- 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_69f22497341481909c21ba329fadaa6b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68716689c81909ec5cd834b5bff00 |
completed | May 2, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:11 p.m.