Triple
T25692804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pancharatra Sampradaya |
E644242
|
entity |
| Predicate | hasRitualTextType |
P162897
|
FINISHED |
| Object | Samhita |
—
|
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: Samhita | Statement: [Pancharatra Sampradaya, hasRitualTextType, Samhita]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRitualTextType Context triple: [Pancharatra Sampradaya, hasRitualTextType, Samhita]
-
A.
hasRitualType
Indicates that an entity is associated with, or classified by, a particular type or category of ritual.
-
B.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
C.
hasRitualRule
Indicates that an entity is governed by, or associated with, a specific ritual rule or prescribed ceremonial guideline.
-
D.
hasRitualName
Indicates that an entity is associated with a specific name used in a ritual or ceremonial context.
-
E.
hasRitualElements
Indicates that one entity incorporates, contains, or is characterized by ritualistic components, practices, or features associated with formalized ceremonies or rites.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f62e83045c8190a424a2e401a88e9e |
completed | May 2, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62d886828819080ec2f742b9449e3 |
completed | May 2, 2026, 4:59 p.m. |
Created at: April 21, 2026, 8:30 p.m.