Triple
T37651971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opele chain |
E937197
|
entity |
| Predicate | usedInDiasporaTraditions |
P101627
|
FINISHED |
| Object | Candomblé |
—
|
NE NERFINISHED |
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: Candomblé | Statement: [Opele chain, usedInDiasporaTraditions, Candomblé]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInDiasporaTraditions Context triple: [Opele chain, usedInDiasporaTraditions, Candomblé]
-
A.
presentInDiasporaTraditions
chosen
Indicates that something continues to exist or be practiced within the cultural traditions of a dispersed (diaspora) community.
-
B.
hasFeastTraditionWith
Indicates a relationship where two entities share or participate in a customary feast or celebratory meal tradition together.
-
C.
languageUsedInRituals
Indicates that a particular language is employed as the medium of speech, chant, or recitation during specific rituals or ceremonial practices.
-
D.
usedInLiturgy
Indicates that something is employed or incorporated as part of a formal religious liturgy or worship service.
-
E.
traditionallyUsedBy
Indicates that something has been customarily or historically used by a particular person, group, or culture over time.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff2fbae9b48190847eefa1c227d43e |
completed | May 9, 2026, 12:59 p.m. |
| PD | Predicate disambiguation | batch_69ff2f2218048190a32224a648182b5d |
completed | May 9, 2026, 12:57 p.m. |
Created at: May 3, 2026, 4:18 p.m.