Triple
T25693434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brahma Sambandha |
E644256
|
entity |
| Predicate | worshipsAs |
P10015
|
FINISHED |
| Object | supreme Brahman |
—
|
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: supreme Brahman | Statement: [Brahma Sambandha, worshipsAs, supreme Brahman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshipsAs Context triple: [Brahma Sambandha, worshipsAs, supreme Brahman]
-
A.
worshipsDeity
Indicates that one entity reveres, honors, or performs religious devotion toward another entity regarded as a deity.
-
B.
worshippedIn
Indicates that a particular deity, figure, or object of reverence is the focus of religious or spiritual worship within a specified place or context.
-
C.
worshipedAs
chosen
Indicates that one entity regards and treats another as a deity or sacred figure, offering reverence, devotion, or religious honor.
-
D.
worshippedAs
Indicates that one entity is regarded and treated with religious reverence or devotion by another entity.
-
E.
worshippedThrough
Indicates that one entity is venerated, honored, or worshipped by means of, or via the medium of, another entity (such as a ritual, object, place, or intermediary).
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 21, 2026, 8:31 p.m.