Triple
T6218426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selk'nam |
E139048
|
entity |
| Predicate | religiousCeremonyFeature |
P65752
|
FINISHED |
| Object | gendered ritual roles |
—
|
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: gendered ritual roles | Statement: [Selk'nam, religiousCeremonyFeature, gendered ritual roles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousCeremonyFeature Context triple: [Selk'nam, religiousCeremonyFeature, gendered ritual roles]
-
A.
religiousEvent
Indicates that an event is related to religious practices, observances, or ceremonies.
-
B.
religiousFunction
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
-
C.
ritualStructure
Indicates a relationship where an entity is a structure or built feature specifically used for performing rituals or ceremonial practices.
-
D.
religiousActivity
Indicates participation in, performance of, or association with practices, rituals, or behaviors related to a religion or faith tradition.
-
E.
ritualActivities
chosen
Indicates that one entity engages in, performs, or is associated with ritualistic or ceremonial activities in relation to another entity or context.
- 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_69c008aecb0c81909984b48f733ce8ae |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062a481908190a1418d9fcfaf8137 |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055fdea3c81908f5d910f0d36234a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:21 p.m.