Triple
T32391919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maya priesthood |
E827694
|
entity |
| Predicate | performedRitualType |
P42159
|
FINISHED |
| Object | bloodletting rituals |
—
|
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: bloodletting rituals | Statement: [Maya priesthood, performedRitualType, bloodletting rituals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedRitualType Context triple: [Maya priesthood, performedRitualType, bloodletting rituals]
-
A.
hasRitualType
chosen
Indicates that an entity is associated with, or classified by, a particular type or category of ritual.
-
B.
ritualOutcome
Indicates the result or consequence produced by performing a particular ritual.
-
C.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
D.
ritualsDirectedAt
Indicates that certain rituals are performed with a specific entity, object, or target as their intended focus or recipient.
-
E.
ritualCategory
Indicates the classification relationship that assigns a ritual to a specific ritual type or category.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: May 1, 2026, 12:52 a.m.