Triple
T12960858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tertius Lydgate |
E310138
|
entity |
| Predicate | medicalInterest |
P66206
|
FINISHED |
| Object | Reform of medical practice |
—
|
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: Reform of medical practice | Statement: [Tertius Lydgate, medicalInterest, Reform of medical practice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: medicalInterest Context triple: [Tertius Lydgate, medicalInterest, Reform of medical practice]
-
A.
medicalPractice
Indicates a relationship where an entity engages in or carries out the professional provision of medical care or services.
-
B.
subjectInterest
chosen
Indicates that the subject has an interest in, or is concerned with, the object.
-
C.
clinicalEmphasis
Indicates a focus or priority placed on clinical aspects, practices, or outcomes within a given context or activity.
-
D.
focusesOnMedicalCare
Indicates that one entity directs attention, resources, or activity specifically toward providing or improving medical care for another entity.
-
E.
medicalCar
Indicates that an entity is a vehicle used for providing medical transport or emergency medical services to 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97dba57988190b786ffed55687a72 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:44 p.m.