Triple
T4782432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramcharitmanas |
E106396
|
entity |
| Predicate | venerationStatus |
P8505
|
FINISHED |
| Object | regarded as sacred scripture by many Hindus |
—
|
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: regarded as sacred scripture by many Hindus | Statement: [Ramcharitmanas, venerationStatus, regarded as sacred scripture by many Hindus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: venerationStatus Context triple: [Ramcharitmanas, venerationStatus, regarded as sacred scripture by many Hindus]
-
A.
venerationType
Indicates the specific manner or category of reverence or worship directed toward an entity.
-
B.
veneratedBy
chosen
Indicates that one entity is regarded with deep respect, reverence, or worship by another entity.
-
C.
veneratedFor
Indicates that one entity is highly respected, honored, or revered because of a particular quality, achievement, or characteristic of another entity.
-
D.
venerationPeriod
Indicates the span of time during which an entity is or was actively venerated, revered, or worshipped.
-
E.
veneratedAt
Indicates that an entity is honored, revered, or worshipped at a particular place or institution.
- 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd69237f80819090713ed62653fb75 |
completed | March 20, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69bd622be1388190ab5511b589c878c0 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.