Triple
T17980152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puttur |
E449578
|
entity |
| Predicate | healthcareSpecialization |
P466
|
FINISHED |
| Object | orthopedic traditional treatment |
—
|
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: orthopedic traditional treatment | Statement: [Puttur, healthcareSpecialization, orthopedic traditional treatment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: healthcareSpecialization Context triple: [Puttur, healthcareSpecialization, orthopedic traditional treatment]
-
A.
medicalPractice
Indicates a relationship where an entity engages in or carries out the professional provision of medical care or services.
-
B.
supportsMedicalSpecialty
Indicates that one entity provides resources, infrastructure, or services that enable or facilitate the practice or development of a particular medical specialty.
-
C.
clinicalRole
Indicates the specific function, responsibility, or position an entity holds within a clinical or healthcare context.
-
D.
healthcareType
Indicates the category or kind of healthcare service, system, or coverage associated with an entity.
-
E.
hasSpecialty
chosen
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b202aab88190b44851808c75a848 |
completed | April 19, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.