Triple
T2670398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ifa |
E55732
|
entity |
| Predicate | hasPractitioner |
P37643
|
FINISHED |
| Object | babalawo |
—
|
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: babalawo | Statement: [Ifa, hasPractitioner, babalawo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPractitioner Context triple: [Ifa, hasPractitioner, babalawo]
-
A.
associatedWithPractice
Indicates a relationship in which an entity is connected or linked to a particular practice, activity, or customary way of doing something.
-
B.
hasHealthcareProvider
Indicates that one entity receives healthcare services or medical oversight from another entity acting as its healthcare provider.
-
C.
notablePractitioner
Indicates that an entity is a well-known or distinguished practitioner of a particular field, discipline, or activity.
-
D.
hasSpecialty
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
-
E.
primaryPractitioners
chosen
Indicates the entities that are the main or most directly responsible practitioners of a given activity, field, or practice in relation to another entity.
- 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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd98d32ac8190b8edd9421b706532 |
completed | March 7, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69abd8190ad481908f3e14ac84d0940a |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.