Triple
T20514994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shinto priests |
E503662
|
entity |
| Predicate | performRitualType |
P4193
|
FINISHED |
| Object | purification rites |
—
|
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: purification rites | Statement: [Shinto priests, performRitualType, purification rites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performRitualType Context triple: [Shinto priests, performRitualType, purification rites]
-
A.
initiatesRitual
Indicates that one entity begins or sets in motion a ritual involving one or more other entities.
-
B.
hasRitual
chosen
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
C.
ritualOutcome
Indicates the result or consequence produced by performing a particular ritual.
-
D.
hasRitualType
Indicates that an entity is associated with, or classified by, a particular type or category of ritual.
-
E.
hasRituals
Indicates that one entity performs, observes, or is associated with specific rituals 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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69f4133048190abb777be4b65c2c4 |
completed | April 20, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:36 a.m.