Triple
T19594306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shruti |
E470311
|
entity |
| Predicate | hasCategoryRole |
P15481
|
FINISHED |
| Object | canonical revelation in Hinduism |
—
|
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: canonical revelation in Hinduism | Statement: [Shruti, hasCategoryRole, canonical revelation in Hinduism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCategoryRole Context triple: [Shruti, hasCategoryRole, canonical revelation in Hinduism]
-
A.
hasCategoryGroup
Indicates that something is associated with, or belongs to, a broader grouping of related categories.
-
B.
hasCategoryOn
chosen
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
C.
hasCategoryWithin
Indicates that one category is contained within or is a subcategory of another category.
-
D.
hasCategoryLevel
Indicates that something is associated with a specific hierarchical category or tier within a classification system.
-
E.
containsCategory
Indicates that one entity includes or encompasses a specific category as part of its classification or organizational structure.
- 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_69e640793cd88190b9b84491bfb2493f |
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.