Triple
T27077865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D.O. |
E685511
|
entity |
| Predicate | holderCanPracticeAs |
P89206
|
FINISHED |
| Object | physician |
—
|
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: physician | Statement: [D.O., holderCanPracticeAs, physician]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderCanPracticeAs Context triple: [D.O., holderCanPracticeAs, physician]
-
A.
licensedToPractice
chosen
Indicates that an entity has been officially authorized by a relevant authority to perform a particular professional practice or activity.
-
B.
retainsPracticeOf
Indicates that an entity continues to uphold or maintain a particular practice, custom, or way of doing things over time.
-
C.
administeredInPracticeBy
Indicates that a medical treatment, procedure, or intervention is carried out or delivered by a specific healthcare practice or provider entity.
-
D.
requiresLicenseForPractice
Indicates that engaging in the specified professional practice is legally contingent upon holding a valid license.
-
E.
hasLanguageOfPractice
Indicates that an entity uses or operates in a particular language as its regular or primary medium of practice.
- 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6231742748190929446f701a0ba50 |
completed | May 2, 2026, 4:15 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:32 a.m.