Triple
T23256891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bondo society |
E581897
|
entity |
| Predicate | riteOfPassageFor |
P111251
|
FINISHED |
| Object | pubescent girls |
—
|
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: pubescent girls | Statement: [Bondo society, riteOfPassageFor, pubescent girls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riteOfPassageFor Context triple: [Bondo society, riteOfPassageFor, pubescent girls]
-
A.
ritesOfPassage
chosen
Indicates a relationship where an entity undergoes or is associated with formal ceremonies or rituals that mark a significant transition or change in social or life status.
-
B.
reasonForPassage
Indicates the underlying cause, motivation, or purpose that explains why a particular passage or movement occurred.
-
C.
guardedPassage
Indicates that access through a passage is controlled or protected by a guard or security presence.
-
D.
soughtPassage
Indicates that one entity attempted to obtain or gain access to a particular passage, route, or way through something.
-
E.
passage
Indicates that an entity moves through, across, or past another entity or spatial region.
- 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_69e246079f58819085eaa9c260906880 |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f194c5f5bc8190ac8776f7f7430209 |
completed | April 29, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:11 p.m.