Triple
T12152750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bibliotheca Medicinae Practicae |
E289497
|
entity |
| Predicate | eraOfLiteratureCovered |
P56599
|
FINISHED |
| Object | early modern medicine |
—
|
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 medicine | Statement: [Bibliotheca Medicinae Practicae, eraOfLiteratureCovered, early modern medicine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfLiteratureCovered Context triple: [Bibliotheca Medicinae Practicae, eraOfLiteratureCovered, early modern medicine]
-
A.
literaryPeriodOfWork
chosen
Indicates the literary period or movement to which a particular work belongs.
-
B.
literarySubject
Indicates that one entity serves as the subject, topic, or focus of a literary work created by another entity.
-
C.
activeYearsInLiterature
Indicates the span of years during which an entity was actively producing or contributing to literary works.
-
D.
literaryCenter
Indicates that a location functions as a primary hub or focal point for literary activity, such as writing, publishing, or literary culture.
-
E.
inLiterature
Indicates that a work, concept, or entity is mentioned, discussed, or represented within a piece of literature.
- 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_69d6ab4c6710819097a9d228382dde43 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69d9150c18148190bf8152189c0e5fca |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:49 p.m.