Triple
T37635751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salaga |
E936482
|
entity |
| Predicate | healthFacilities |
P10262
|
FINISHED |
| Object | has a district hospital or health centre |
—
|
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: has a district hospital or health centre | Statement: [Salaga, healthFacilities, has a district hospital or health centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: healthFacilities Context triple: [Salaga, healthFacilities, has a district hospital or health centre]
-
A.
clinicalFacilities
Indicates that one entity provides, contains, or is associated with clinical facilities used for medical or healthcare services by another entity.
-
B.
hospitalLocation
Indicates the geographic place or address where a hospital is situated.
-
C.
healthSystem
Indicates a relationship where an entity functions as, belongs to, or is managed within a particular health care system or network.
-
D.
healthServiceProvider
Indicates that one entity provides health-related services or care to another entity.
-
E.
hasMedicalCenter
chosen
Indicates that an entity possesses, hosts, or is associated with a medical center facility.
- 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_69f76ed31d8881908405da6c6d2f0463 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:18 p.m.