Triple
T7511695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OHSU School of Dentistry |
E177534
|
entity |
| Predicate | hasClinicalService |
P77388
|
FINISHED |
| Object | general dentistry |
—
|
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: general dentistry | Statement: [OHSU School of Dentistry, hasClinicalService, general dentistry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClinicalService Context triple: [OHSU School of Dentistry, hasClinicalService, general dentistry]
-
A.
hasDiagnosticService
Indicates that an entity provides, is associated with, or makes use of a diagnostic service for detecting, analyzing, or identifying issues or conditions.
-
B.
hasClinicalUnit
Indicates that an entity is associated with or belongs to a specific clinical unit or department within a healthcare setting.
-
C.
hasMedicalCenter
Indicates that an entity possesses, hosts, or is associated with a medical center facility.
-
D.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
E.
hasHealthcareProvider
Indicates that one entity receives healthcare services or medical oversight from another entity acting as its healthcare provider.
- F. None of above. chosen
Provenance (4 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_69c69f276b108190af2cc790b6554544 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f5d33960819089a10c1149abf4b2 |
completed | March 27, 2026, 9:25 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d44e9481909813e073b194f6f4 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f574d8a8819095749518dad13791 |
completed | March 27, 2026, 9:24 p.m. |
Created at: March 27, 2026, 3:45 p.m.