Triple
T11797103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | babalawo |
E280527
|
entity |
| Predicate | requiresInitiation |
P70872
|
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: [babalawo, requiresInitiation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresInitiation Context triple: [babalawo, requiresInitiation, yes]
-
A.
requiresInitiationIn
Indicates that one entity must be initiated, started, or activated within the context, scope, or environment defined by another entity.
-
B.
requiresInitialization
chosen
Indicates that one entity cannot be correctly used or executed until a specific setup or initialization process has been completed.
-
C.
hasInitiation
Indicates that one entity initiates, starts, or triggers an action, process, or relationship involving another entity.
-
D.
requiresTraining
Indicates that one entity can only be properly or legitimately used, performed, or engaged with if the other entity has first received appropriate training.
-
E.
requiresNotificationTo
Indicates that one entity must send a notification to another entity before or when a certain condition, event, or action occurs.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5a1cda0819092d66a82fd882786 |
completed | April 10, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69d8a2491f048190853239bc05090bf4 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.