Triple
T5737225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dharma |
E126529
|
entity |
| Predicate | viewInSikhism |
P62707
|
FINISHED |
| Object | righteous living in accordance with divine will |
—
|
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: righteous living in accordance with divine will | Statement: [Dharma, viewInSikhism, righteous living in accordance with divine will]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewInSikhism Context triple: [Dharma, viewInSikhism, righteous living in accordance with divine will]
-
A.
viewOnDharma
chosen
Indicates a relationship where an entity holds a particular perspective, interpretation, or stance regarding Dharma (moral or religious duty/principle).
-
B.
viewsSamadhiAs
Indicates considering or regarding Samadhi (a state of meditative absorption) in a particular way, role, or significance.
-
C.
viewOnBuddha
Indicates that an entity holds a particular perspective, opinion, or interpretive stance regarding Buddha.
-
D.
scriptForSikhReligiousTexts
Indicates the script or writing system used to write Sikh religious texts.
-
E.
viewOnGanesha
Indicates a perspective, opinion, or belief that an entity holds regarding Ganesha.
- 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_69c0083082288190b7478cead6b5430a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0255ad6f48190977bf4f037110aa3 |
completed | March 22, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69c021c8195481909419808b002628aa |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:47 p.m.