Triple
T28182147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centre hospitalier de Guéret |
E716061
|
entity |
| Predicate | offersSpecialties |
P144958
|
FINISHED |
| Object | internal medicine |
—
|
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: internal medicine | Statement: [Centre hospitalier de Guéret, offersSpecialties, internal medicine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersSpecialties Context triple: [Centre hospitalier de Guéret, offersSpecialties, internal medicine]
-
A.
offersSpecialtyCare
chosen
Indicates that an entity provides specialized or advanced care services beyond general or primary care.
-
B.
hasSpecialty
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
-
C.
offersDiscipline
Indicates that one entity provides or makes available a particular field of study, training, or area of specialization to another entity.
-
D.
openingSpecialty
Indicates the specific area of focus, expertise, or type associated with an opening (such as a job, position, or opportunity).
-
E.
offersServiceIn
Indicates that a provider makes a particular service available within a specified location or jurisdiction.
- 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 27, 2026, 10:20 p.m.