Triple
T19594178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soma sacrifice |
E470309
|
entity |
| Predicate | ritualLiteratureType |
P76648
|
FINISHED |
| Object | Srauta ritual |
—
|
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: Srauta ritual | Statement: [Soma sacrifice, ritualLiteratureType, Srauta ritual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ritualLiteratureType Context triple: [Soma sacrifice, ritualLiteratureType, Srauta ritual]
-
A.
religiousLiteratureType
Indicates the specific category or type of religious literature associated with an entity, such as scripture, commentary, liturgy, or devotional text.
-
B.
ritualCategory
chosen
Indicates the classification relationship that assigns a ritual to a specific ritual type or category.
-
C.
literatureType
Indicates the specific category or genre of literature that characterizes or classifies a given work or text.
-
D.
ritualCharacteristics
Indicates the defining features, practices, or attributes that characterize a particular ritual.
-
E.
ritualStructure
Indicates a relationship where an entity is a structure or built feature specifically used for performing rituals or ceremonial practices.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640782e2c8190b5baef07a2bdd015 |
completed | April 20, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.