Triple
T23658395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandhi Puja |
E584371
|
entity |
| Predicate | symbolismOfLamps |
P153062
|
FINISHED |
| Object | invocation of divine energy |
—
|
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: invocation of divine energy | Statement: [Sandhi Puja, symbolismOfLamps, invocation of divine energy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolismOfLamps Context triple: [Sandhi Puja, symbolismOfLamps, invocation of divine energy]
-
A.
lightingOfLampsSignifies
Indicates that the act of lighting lamps serves as a sign, symbol, or marker of a particular event, state, or significance.
-
B.
lanternSymbolizes
Indicates that a lantern serves as a symbol representing a particular idea, quality, or concept in relation to something else.
-
C.
symbolismOfChurch
Indicates the symbolic meaning or representational significance that a church holds within a given context.
-
D.
languageOfSymbolism
Indicates that one entity is the language in which the symbolic meaning or symbolism of another entity is expressed or encoded.
-
E.
typeOfLampsUsed
Indicates the specific kinds or categories of lamps that are utilized in a given context or system.
- F. None of above. chosen
Provenance (4 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b35ce4bc81909a26bc7e44a929d8 |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f1233300bc8190ac1639bdca1d7d99 |
completed | April 28, 2026, 9:14 p.m. |
Created at: April 17, 2026, 6:49 p.m.