Triple
T11579910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Candomblé |
E274597
|
entity |
| Predicate | hasInitiationPractice |
P79048
|
FINISHED |
| Object | seclusion of initiates |
—
|
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: seclusion of initiates | Statement: [Candomblé, hasInitiationPractice, seclusion of initiates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInitiationPractice Context triple: [Candomblé, hasInitiationPractice, seclusion of initiates]
-
A.
hasInitiation
Indicates that one entity initiates, starts, or triggers an action, process, or relationship involving another entity.
-
B.
initiationPractice
chosen
Indicates the act of beginning, launching, or formally starting a particular practice, process, or activity.
-
C.
hasPractices
Indicates that an entity engages in, follows, or carries out specific practices, methods, or customary ways of doing things.
-
D.
initiationStatus
Indicates the current state or phase of beginning or starting a process, activity, or relationship between entities.
-
E.
requiresPractice
Indicates that performing or mastering one entity depends on engaging in repeated practice or training involving 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8904b46288190890ecafd6ceb0c3d |
completed | April 10, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.