Triple
T4993616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaunakiya |
E112190
|
entity |
| Predicate | hasScripturalCategory |
P6836
|
FINISHED |
| Object | Śruti |
—
|
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: Śruti | Statement: [Shaunakiya, hasScripturalCategory, Śruti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScripturalCategory Context triple: [Shaunakiya, hasScripturalCategory, Śruti]
-
A.
hasScripture
Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
-
B.
regardedAsScriptureBy
Indicates that something is considered to be sacred scripture or canonical religious text by a particular person, group, or tradition.
-
C.
consideredScriptureBy
Indicates that one party regards or recognizes a text or writing as sacred scripture.
-
D.
scriptureType
chosen
Indicates the classification or category of a scripture in relation to its type or genre.
-
E.
scripturalStatus
Indicates the relationship between a text and its recognition or classification as scriptural, canonical, or authoritative within a religious or doctrinal tradition.
- 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_69bd4432b32c81909f3b3c6bd10f0653 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74249a8c8190952680aee06a9286 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71492dec8190af4c27a3043b35cc |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:34 p.m.