Triple
T38607882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mbum peoples |
E934395
|
entity |
| Predicate | traditionalCulturalPractice |
P1114
|
FINISHED |
| Object | initiation rites |
—
|
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: initiation rites | Statement: [Mbum peoples, traditionalCulturalPractice, initiation rites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalCulturalPractice Context triple: [Mbum peoples, traditionalCulturalPractice, initiation rites]
-
A.
cultPractices
Indicates involvement in or performance of rituals, beliefs, or behaviors associated with a cult.
-
B.
culturalTradition
chosen
Indicates a relationship where certain practices, beliefs, or customs are recognized as part of a shared cultural heritage passed down within a group or society.
-
C.
cultOrTradition
Indicates that one entity is a cult or tradition associated with, practiced by, or characterizing another entity.
-
D.
practicedTradition
Indicates that an entity engages in or carries out a particular tradition as a customary or repeated practice.
-
E.
citesTradition
Indicates that one entity references, appeals to, or draws authority from a tradition associated with 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_69f76eccd6d081909ccce171011739a1 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00144238708190acbec3f791cc873e |
completed | May 10, 2026, 5:14 a.m. |
| PD | Predicate disambiguation | batch_6a00120244a4819090ef39070aba9d99 |
completed | May 10, 2026, 5:05 a.m. |
Created at: May 3, 2026, 4:32 p.m.