Triple
T25685338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donyi-Polo |
E644052
|
entity |
| Predicate | hasRitualSpecialists |
P162110
|
FINISHED |
| Object | shamans |
—
|
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: shamans | Statement: [Donyi-Polo, hasRitualSpecialists, shamans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRitualSpecialists Context triple: [Donyi-Polo, hasRitualSpecialists, shamans]
-
A.
hasRitualCustodian
Indicates that one entity serves as the designated custodian or caretaker responsible for performing, preserving, or overseeing the rituals associated with another entity.
-
B.
hasRitualSpace
Indicates that an entity possesses or is associated with a designated space used for ritual or ceremonial activities.
-
C.
hasRitualElements
Indicates that one entity incorporates, contains, or is characterized by ritualistic components, practices, or features associated with formalized ceremonies or rites.
-
D.
hasRitualRoleIn
Indicates that an entity serves a specific ritual function or role within a particular ritual, ceremony, or sacred practice.
-
E.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
- 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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 21, 2026, 8:07 p.m.