Triple
T13705916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bassa |
E328639
|
entity |
| Predicate | ritesOfPassage |
P111251
|
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: [Bassa, ritesOfPassage, initiation ceremonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ritesOfPassage Context triple: [Bassa, ritesOfPassage, initiation ceremonies]
-
A.
numberOfPassages
Indicates the total count of distinct passages associated with or contained within a given entity or context.
-
B.
נקראים
Indicates that entities are named, called, or referred to by a particular term or title.
-
C.
guardedPassage
Indicates that access through a passage is controlled or protected by a guard or security presence.
-
D.
scriptureContributedTo
Indicates that an entity played a role in creating, authoring, or otherwise contributing content to a particular scripture or sacred text.
-
E.
soughtPassage
Indicates that one entity attempted to obtain or gain access to a particular passage, route, or way through something.
- F. None of above. chosen
Provenance (4 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dcad17732c8190bbd0d73107711c99 |
completed | April 13, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:54 p.m.