Triple
T38224256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Medical Centre Bida |
E1012095
|
entity |
| Predicate | governmentHospital |
P19124
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Federal Medical Centre Bida, governmentHospital, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentHospital Context triple: [Federal Medical Centre Bida, governmentHospital, true]
-
A.
hospitalLocation
Indicates the geographic place or address where a hospital is situated.
-
B.
isPublicHospital
chosen
Indicates that a hospital is owned, funded, or operated by a government or public authority rather than by private entities.
-
C.
majorHospital
Indicates that a hospital holds a primary or leading status within a healthcare system or region, typically due to its size, capacity, or range of services.
-
D.
healthSystem
Indicates a relationship where an entity functions as, belongs to, or is managed within a particular health care system or network.
-
E.
hospitalFunction
Indicates the specific medical or administrative role, service, or operational purpose that a hospital performs.
- 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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.