Triple
T22594390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diné |
E574634
|
entity |
| Predicate | ceremonialSpecialist |
P3343
|
FINISHED |
| Object | medicine person |
—
|
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: medicine person | Statement: [Diné, ceremonialSpecialist, medicine person]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonialSpecialist Context triple: [Diné, ceremonialSpecialist, medicine person]
-
A.
ceremonialFocus
Indicates that one entity serves as the central object, site, or theme around which a ceremony or ritual is organized or directed.
-
B.
ceremonialRole
chosen
Indicates that an entity holds a formal, often symbolic or honorific, position or function within a ceremony or ritual context.
-
C.
ceremonialUse
Indicates that something is used in a ritual, religious, or formal ceremony rather than for ordinary or practical purposes.
-
D.
ceremonialLife
Indicates involvement in or association with formal rituals, traditions, or ceremonial practices within a social or cultural context.
-
E.
ceremonialRoleInvolves
Indicates that a ceremonial role includes or entails performing a particular action, duty, or function as part of that ceremony.
- 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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f16164d690819096f7c4efb6cedad9 |
completed | April 29, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:49 p.m.