Triple
T7947342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Department of Periodontology |
E184529
|
entity |
| Predicate | clinicalActivity |
P77388
|
FINISHED |
| Object | diagnosis of periodontal disease |
—
|
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: diagnosis of periodontal disease | Statement: [Department of Periodontology, clinicalActivity, diagnosis of periodontal disease]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clinicalActivity Context triple: [Department of Periodontology, clinicalActivity, diagnosis of periodontal disease]
-
A.
clinicalRole
Indicates the specific function, responsibility, or position an entity holds within a clinical or healthcare context.
-
B.
medicalEvent
Indicates that a specific health-related occurrence or clinical incident has taken place involving one or more entities.
-
C.
clinicalForm
Indicates the specific clinical manifestation or presentation type associated with a medical condition or case.
-
D.
practiceElement
Indicates that one entity is a component, step, or sub-activity within a broader practice or procedure involving another entity.
-
E.
hasClinicalService
chosen
Indicates that an entity provides, offers, or is associated with a specific clinical service.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b2abdbc819085ae53826d36af3b |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae9361bc48190886b7681e563d46b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:09 p.m.