Triple
T11122162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vishwamanava |
E263041
|
entity |
| Predicate | aimsToTranscend |
P56568
|
FINISHED |
| Object | caste divisions |
—
|
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: caste divisions | Statement: [Vishwamanava, aimsToTranscend, caste divisions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimsToTranscend Context triple: [Vishwamanava, aimsToTranscend, caste divisions]
-
A.
spiritualAchievement
Indicates the attainment or realization of a significant level of spiritual growth, insight, or enlightenment by an entity.
-
B.
spiritualMeans
Indicates that one entity serves as a spiritual method, medium, or pathway through which another entity attains or engages in a spiritual state, goal, or practice.
-
C.
inTheSpiritOf
Indicates that one entity acts, is created, or is characterized in a manner that follows the style, principles, or intent exemplified by another entity.
-
D.
spiritualityType
Indicates the specific kind or category of spirituality associated with an entity.
-
E.
spiritualQuest
chosen
Indicates a process in which an entity actively seeks deeper spiritual understanding, growth, or enlightenment.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79afa0ab88190ab6d61df8cf485ec |
completed | April 9, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69d7441efe948190ae4ab020121e169d |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:28 p.m.