Triple
T28381801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr George Mukhari Academic Hospital |
E718907
|
entity |
| Predicate | referralFrom |
P125382
|
FINISHED |
| Object | district hospitals |
—
|
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: district hospitals | Statement: [Dr George Mukhari Academic Hospital, referralFrom, district hospitals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referralFrom Context triple: [Dr George Mukhari Academic Hospital, referralFrom, district hospitals]
-
A.
referralBy
Indicates that one entity was referred, recommended, or directed to another entity by a specific source or agent.
-
B.
receivesReferralsFrom
chosen
Indicates that one entity is the recipient of referrals that originate from another entity.
-
C.
referralRelationship
Indicates a relationship in which one entity directs or recommends another entity to a third party for services, information, or further action.
-
D.
referredTo
Indicates that one entity has mentioned, directed attention to, or cited another entity as a point of reference.
-
E.
refersToPersonFrom
Indicates that one entity makes reference to, mentions, or is about a person originating from or associated with a particular place or group.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 28, 2026, 1:07 a.m.