Triple
T4523315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panchayatana puja |
E103316
|
entity |
| Predicate | recognizesDeityForm |
P5606
|
FINISHED |
| Object | saguna 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: saguna Brahman | Statement: [Panchayatana puja, recognizesDeityForm, saguna Brahman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizesDeityForm Context triple: [Panchayatana puja, recognizesDeityForm, saguna Brahman]
-
A.
representsDeity
Indicates that one entity serves as a symbolic, artistic, or conceptual depiction of a deity associated with another entity.
-
B.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
C.
hasDeity
chosen
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
D.
hasConsortDeityForm
Indicates that an entity has a consort specifically in their deity or divine form.
-
E.
hasComponentDeity
Indicates that an entity (such as a religion, mythology, or pantheon) includes a particular deity as one of its constituent or associated divine figures.
- 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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd574d7c2481909049955ca47613a6 |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd521cf77c819083852de3094d1377 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:02 p.m.