Triple
T7327575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RJD |
E168912
|
entity |
| Predicate | hasMedicalServices |
P72534
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [RJD, hasMedicalServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMedicalServices Context triple: [RJD, hasMedicalServices, yes]
-
A.
hasMedicalCenter
Indicates that an entity possesses, hosts, or is associated with a medical center facility.
-
B.
hasDiagnosticService
Indicates that an entity provides, is associated with, or makes use of a diagnostic service for detecting, analyzing, or identifying issues or conditions.
-
C.
hasHealthcareProvider
Indicates that one entity receives healthcare services or medical oversight from another entity acting as its healthcare provider.
-
D.
hasHealthServicesCoordination
Indicates that one entity is responsible for organizing, managing, or facilitating access to health-related services for another entity.
-
E.
hasHealthcareInfrastructure
chosen
Indicates that an entity possesses facilities, systems, and resources necessary to deliver healthcare services.
- 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_69c68a54cacc81908e3b773441f19566 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f0a755e88190a50126e2d1d6d4cb |
completed | March 27, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69c6e77230048190b2c29ca6b3a65b8e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:03 p.m.