Triple
T27740803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copperbelt mining towns |
E701846
|
entity |
| Predicate | haveHealthFacilities |
P72534
|
FINISHED |
| Object | clinics |
—
|
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: clinics | Statement: [Copperbelt mining towns, haveHealthFacilities, clinics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveHealthFacilities Context triple: [Copperbelt mining towns, haveHealthFacilities, clinics]
-
A.
hasHealthcareInfrastructure
chosen
Indicates that an entity possesses facilities, systems, and resources necessary to deliver healthcare services.
-
B.
hasPublicHealthInfrastructure
Indicates that an entity possesses systems, facilities, and organizational structures dedicated to protecting and promoting public health.
-
C.
hasCrisisFacility
Indicates that an entity possesses or includes a dedicated facility or service for handling crises or emergency situations.
-
D.
hasHealthcareServicesIn
Indicates that a healthcare provider or organization offers or operates healthcare services within a specified location or area.
-
E.
hasHealthArea
Indicates that an entity is associated with, or falls within the scope of, a particular health-related domain or area of concern.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 4:10 p.m.