Triple
T23257025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sande society |
E581900
|
entity |
| Predicate | membershipAcquiredBy |
P24118
|
FINISHED |
| Object | initiation ceremony |
—
|
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 ceremony | Statement: [Sande society, membershipAcquiredBy, initiation ceremony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membershipAcquiredBy Context triple: [Sande society, membershipAcquiredBy, initiation ceremony]
-
A.
membershipRecordedBy
Indicates that the recording or documentation of a membership was carried out or created by a specific agent or system.
-
B.
membershipBy
Indicates that one entity holds membership or belongs to a group, organization, or collection defined by another entity.
-
C.
memberBecame
chosen
Indicates that an entity transitioned into becoming a member of a group, organization, or collection at a specific point in time.
-
D.
membershipPublishedIn
Indicates that a membership or affiliation is formally recorded or made public within a specific publication or published source.
-
E.
membershipOrigin
Indicates the source or basis from which an entity’s membership in a group, organization, or category is derived.
- 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.