Triple
T23271040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ambo |
E588288
|
entity |
| Predicate | traditionalRite |
P1104
|
FINISHED |
| Object | initiation ceremonies |
—
|
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 ceremonies | Statement: [Ambo, traditionalRite, initiation ceremonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalRite Context triple: [Ambo, traditionalRite, initiation ceremonies]
-
A.
traditionalPriesthood
Indicates that an entity holds or is associated with a priestly role rooted in longstanding, customary, or historically established religious practices.
-
B.
dominantRite
Indicates that one religious rite or liturgical tradition holds primary or prevailing status over others within a given context or community.
-
C.
ordinationRite
Indicates the formal religious ceremony or ritual through which a person is conferred an office or ordained to a specific role.
-
D.
liturgicalTradition
chosen
Indicates the specific religious rite or ceremonial tradition according to which a worship service, practice, or community operates.
-
E.
notableRite
Indicates that an entity is associated with a significant or distinguished ritual, ceremony, or formal rite.
- 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1957418fc819085ee528622e0c6de |
completed | April 29, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:45 p.m.