Triple
T874020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brahma |
E18875
|
entity |
| Predicate | worshipDecline |
P19208
|
FINISHED |
| Object | classical and later 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: classical and later Hinduism | Statement: [Brahma, worshipDecline, classical and later Hinduism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshipDecline Context triple: [Brahma, worshipDecline, classical and later Hinduism]
-
A.
worship
Indicates a relationship where one entity shows reverence, adoration, or religious devotion toward another entity, often recognizing it as sacred or divine.
-
B.
declineAfter
chosen
Indicates that one entity or value decreases or worsens following another specified event, condition, or point in time.
-
C.
worshipImplication
Indicates that one entity’s worship, reverence, or devotional behavior toward another implies or entails a particular belief, status, or relationship between them.
-
D.
worshipType
Indicates the manner or form in which worship is practiced or expressed in a religious or spiritual context.
-
E.
reopenedForWorship
Indicates that a previously closed or inactive place of worship has been opened again for religious services or rituals.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac992d8c819088800f5a713fa7a4 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8b9b5c81909ac71904f8b8b5cd |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.