Triple
T12715195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Owerri West |
E303817
|
entity |
| Predicate | hasPrimaryHealthCareFacilities |
P65774
|
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: [Owerri West, hasPrimaryHealthCareFacilities, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryHealthCareFacilities Context triple: [Owerri West, hasPrimaryHealthCareFacilities, yes]
-
A.
hasHealthcareInfrastructure
Indicates that an entity possesses facilities, systems, and resources necessary to deliver healthcare services.
-
B.
hasPublicHealthInfrastructure
chosen
Indicates that an entity possesses systems, facilities, and organizational structures dedicated to protecting and promoting public health.
-
C.
hasHealthcareProvider
Indicates that one entity receives healthcare services or medical oversight from another entity acting as its healthcare provider.
-
D.
hasMedicalCenter
Indicates that an entity possesses, hosts, or is associated with a medical center facility.
-
E.
hasOwnHealthSystem
Indicates that an entity operates and controls its own dedicated healthcare system, rather than relying solely on external or shared health 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9620a7554819083784897ff690652 |
completed | April 10, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69d960c088dc8190b0e63312c54e4c6c |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:23 p.m.